Skip to content

chore: adopt gsd agent automation #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pocketrocket merged 1 commit into from
Jul 20, 2026
Merged

chore: adopt gsd agent automation #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions .github/workflows/agent-security.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,18 @@ name: Security Agent

# Triggers Cursor's Security Cloud Agent via API in two modes:
# 1. PR mode — Dependabot/dep-labeled PR → workflow waits + posts report
# 2. Cron mode — weekly Mondays 06:00 UTC, sandbox creates fix PRs/issues
# 2. Cron mode — weekly audit, sandbox creates fix PRs/issues
# (Cursor sandbox can create new PRs/issues but cannot comment on existing
# PRs, so PR-mode requires the workflow to post the report itself.)
#
# The weekly run is NOT self-scheduled here — that would fire on every managed
# repo at the same instant and trip Cursor's concurrent-agent limit. Instead
# the template's weekly-security-dispatch.yml triggers this via workflow_dispatch,
# staggered and throttled under the limit. (cron-mode still runs on dispatch.)

on:
pull_request:
types: [opened, synchronize, labeled]
schedule:
- cron: "0 6 * * 1"
workflow_dispatch:

jobs:
Expand Down