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/sinks)<a href="https://agentmods.dev/commands/allsmog/vuln-scout/sinks"><img src="https://agentmods.dev/badge/commands/allsmog/vuln-scout/sinks.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.00987 |
| Opus 5 | $0.00010 | $0.00494 |
| Sonnet 5 | $0.00004 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
sinks scanned grade A with 1 finding 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Python: os.system, subprocess, os.popen How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sink Search Command
Search the codebase for dangerous functions that could lead to vulnerabilities. Optionally auto-discover logging patterns and sensitive data sources.
Flags
| Flag | Effect |
|---|---|
--discover |
Auto-discover logging patterns and sensitive sources first |
--scope name |
Use pre-created scope file |
Execution
Step 1: Determine Language
If language argument provided:
- Use that language's sink patterns
If no language argument:
- Detect from file extensions using Glob
- Search for: *.php, *.java, *.py, *.js, *.ts, *.cs, *.go, *.rb
Step 1.5: Auto-Discovery Mode (if --discover)
When --discover flag is provided, first identify codebase-specific patterns:
Discover Logging Patterns:
# Go
grep -rhoE "\w+\.(Error|Info|Debug|Warn|Fatal|Log)\w*\s*\(" --include="*.go" | sort | uniq -c | sort -rn | head -10
# Python
grep -rhoE "(logging|logger|log)\.(error|info|debug|warning)\s*\(" --include="*.py" | sort | uniq -c | sort -rn | head -10
# JavaScript/TypeScript
grep -rhoE "(console|logger|log)\.(error|info|debug|warn|log)\s*\(" --include="*.js" --include="*.ts" | sort | uniq -c | sort -rn | head -10
Discover Sensitive Sources:
# Variable names with sensitive patterns
grep -rniE "\b\w*(secret|password|apikey|token|credential|private.?key)\w*\b" --include="*.go" --include="*.py" --include="*.java" --include="*.js" | grep -v "_test" | head -20
Output discovered patterns before running standard sink search.
Step 2: Search for Sinks by Category
For the target language, search these categories in order:
Command Execution (Critical):
- PHP: exec, system, passthru, shell_exec, popen, proc_open
- Java: Runtime.exec, ProcessBuilder
- Python: os.system, subprocess, os.popen
- Node.js: child_process
- .NET: Process.Start
- Go: exec.Command
- Ruby: system, exec, backticks
Code Execution (Critical):
- PHP: eval, assert, create_function, preg_replace with /e
- Java: ScriptEngine.eval, OGNL, MVEL, SpEL
- Python: eval, exec, compile
- Node.js: eval, Function constructor, vm module
- .NET: CSharpCodeProvider, Assembly.Load
- Ruby: eval, instance_eval, class_eval
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.
- 8d ago First seen · 129 lines · 20 tokens per session scan A b33c9294e825
sinks 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 987 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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.