auditor:quick-scan

auditor-skill — Quick Scan

Arguments: $ARGUMENTS

1. Discover the repo and declare scope (OUTPUT-RULES.md Rule 0).
2. If the bundled Trail of Bits plugins are present (test -d "${CLAUDE_PLUGIN_ROOT}/vendor/trailofbits/plugins"), run static-analysis (SAST) over in-scope languages; otherwise run the discovery/grep-commands.md scanners. Any analyzer that builds the target runs in the execution mode recorded at intake (OUTPUT-RULES.md Rule 11a).
3. Evaluate only CRITICAL / HIGH known-vectors for the detected domains — not the full set.
4. Report findings with severity + file:line. State clearly this is a triage pass, not a complete audit, and point to /auditor:audit for full coverage.
5. As a CI gate on a public repository (OUTPUT-RULES.md Rule 11d): post pass/fail only — no finding counts, total or per severity — in PR comments, check annotations, the job log and uploaded artifacts alike, since anyone signed in to GitHub can read all of them. Send finding details through a private channel (private vulnerability reporting, a draft security advisory, or a private repository). If that channel is unavailable, fail the job; never fall back to printing findings in the log.