Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add allsmog/vuln-scout/plugin install vuln-scoutWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/allsmog/vuln-scout/scan)<a href="https://agentmods.dev/commands/allsmog/vuln-scout/scan"><img src="https://agentmods.dev/badge/commands/allsmog/vuln-scout/scan.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.02806 |
| Opus 5 | $0.00010 | $0.01403 |
| Sonnet 5 | $0.00004 | $0.00561 |
| Haiku 4.5 | $0.00002 | $0.00281 |
Grade A, and why
scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan
Run automated static analysis and write the results to .claude/findings.json.
Flags
| Flag | Effect |
|---|---|
--profile |
Use quick (local deterministic rules), deep (installed analyzers), or audit (deterministic baseline for Claude-driven review) |
--tools |
Run api-spec, semgrep, codeql, joern, or a comma-separated combination |
--rules |
Semgrep ruleset override |
--workspace |
Resolve a monorepo workspace before scanning |
--since-commit |
Scan files changed since a commit SHA |
--diff-base |
Backward-compatible alias for diff scans against a git ref |
--exclude |
Extra exclusions |
--suppressions |
Apply .vuln-scout-ignore after aggregation |
--format |
Emit json, sarif, md, html, pr-comment, or badge at the end |
--fail-on |
Exit 2 when unsuppressed finding entries exist at or above the severity |
--output |
Save the final emitted artifact to a file. In Claude plugin workflows, resolve relative output paths under the target workspace when the scan target is not the current directory. |
--json |
Shortcut for --format json |
--secrets |
Run secret scanning (gitleaks/truffleHog) alongside static analysis |
--require-tools |
Fail if any requested tool is unavailable |
--custom-rules |
Generate target-specific Semgrep rules in addition to profile rules |
--extended-detectors |
Run regex-based VulnScout detectors in addition to scanner tools |
--incremental |
Use file-hash cache to skip unchanged files |
--generate-pocs |
Generate proof-of-concept scripts for verified findings |
--no-filter |
Keep low-confidence Semgrep audit results as hotspots instead of dropping them |
--no-semantic-analysis |
Compatibility flag for callers that share /full-audit options; the standalone CLI does not run a Claude semantic analysis phase |
The audit profile does not invoke Claude during the scan phase; semantic review is performed afterward by /vuln-scout:verify or /vuln-scout:full-audit.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 313 lines · 20 tokens per session scan A c33fe7c8b44f
scan is a command published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 2,806 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
fix
Apply code-level fixes for ALL validated findings, one at a time — modifies the target repository's source code.
security-semgrep-setup
Check if Semgrep is installed and working. If not, install it using the best available method. Then log in to Semgrep Pro, enable the Pro engine, and run a local Pro scan in the current directory.
sessions
List all Claude Code sessions across all projects, sorted by most recent. Show project context, date, and the exact resume command for each session.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
init
Install the formatters this repository needs, with every command visible before it runs.