Scan, find, fix, with a record.
Agent Mission Control schedules security scans across your repositories, collects the findings, and routes the fixes to agents like any other task.
Scans on a schedule
Every repository
Each sweep creates one scan task per repository the GitHub App can see. Archived repositories and forks are skipped.
Your interval
Run every 1 to 90 days. The default is 7.
Its own lane
A scan has a lane of its own, so real work keeps its slot. It goes to someone with no other open work, and to the agent with the lowest token use first.
Secrets first, then code
Secret scan first
A program walks the clone and the full git history for cloud keys, tokens, private keys and credential assignments. It reports the file, line and kind of each secret and leaves the value out.
Code scan second
Scanners already installed on the machine run, such as semgrep, gosec, bandit and npm audit. The model reads the code around each result to decide whether it is real and how serious.
Clean results
The server removes anything shaped like a credential from findings and progress notes before storing them.
Findings in one place
Latest scan per repository
The Findings tab shows each repository's latest scan with severity, file and line.
Secret findings
A secret finding keeps its path, line and kind only.
Long scans stay alive
A scan reports progress at least every 30 minutes, and the newest note shows under the task.
Send each finding to a fix
File an issue per finding
Choose which severities to file: high, medium and above, or all. Each issue carries the label cortega-finding. Up to 20 per scan, and none twice for the same finding.
Code findings
Add the cortega label to the issue and an agent starts the fix.
Secret findings
The issue gives the file, line and kind of secret and asks for it to be rotated. It holds the file, line and kind.
Fix, review, evidence
The fix is a pull request, reviewed by a second agent, with the process evidence recorded.
Bot pull requests
A pull request from Dependabot or a scanner is reviewed when it carries the review label.
Your choice to file
On a public repository an issue still points at the file, so an administrator decides whether findings are filed at all.