Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/allsmog/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/create-rule)<a href="https://agentmods.dev/commands/allsmog/vuln-scout/create-rule"><img src="https://agentmods.dev/badge/commands/allsmog/vuln-scout/create-rule.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.00018 | $0.00600 |
| Opus 5 | $0.00009 | $0.00300 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
create-rule 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 7d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Custom Detection Rule
Generate a Semgrep YAML rule from a confirmed vulnerability pattern. The rule captures the anti-pattern so future scans detect similar issues across the codebase.
Usage
/vuln-scout:create-rule VSCOUT-0003
/vuln-scout:create-rule src/api/users.ts:42
/vuln-scout:create-rule VSCOUT-0003 --output .semgrep/rules/ --test
Flags
| Flag | Effect |
|---|---|
finding-id |
Finding ID from .claude/findings.json to generate a rule for |
file:line |
Alternative: specify the vulnerable code location directly |
--output |
Directory to save the rule (default: .claude/custom-rules/) |
--test |
Run the generated rule against the codebase to verify it works |
Workflow
Step 1: Extract the vulnerability pattern
If a finding ID is provided, load it from .claude/findings.json and read the evidence code excerpts.
If a file:line is provided, read the surrounding code context.
Identify:
- The dangerous sink (the function call that is vulnerable)
- The unsafe pattern (how user input reaches the sink)
- The language of the code
Step 2: Generate the Semgrep rule
Create a YAML rule with:
id:vuln-scout.custom.<descriptive-name>patternorpattern-either: captures the anti-patternpattern-not: excludes safe variants (parameterized queries, etc.)message: explains the vulnerability and how to fix itseverity: ERROR for exploitable, WARNING for potentiallanguages: detected from the source filemetadata:category: security,cwe,confidencefix(optional): auto-fix pattern if applicable
Step 3: Test the rule (if --test)
semgrep --config <generated-rule-file> --json <target-path>
Verify:
- The rule catches the original finding
- False positive rate is acceptable (< 20%)
- The rule works on the correct language
Step 4: Save
Write the rule to the output directory. Report the file path so it can be committed and used in future scans.
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.
- 7d ago First seen · 74 lines · 18 tokens per session scan A 0d99648dc2f9
create-rule is a command published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 600 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.