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/scope)<a href="https://agentmods.dev/commands/allsmog/vuln-scout/scope"><img src="https://agentmods.dev/badge/commands/allsmog/vuln-scout/scope/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/allsmog/vuln-scout/scope"><img src="https://agentmods.dev/badge/commands/allsmog/vuln-scout/scope.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.07976 |
| Opus 5.5 | $0.00008 | $0.03190 |
| Sonnet 5.5 | $0.00004 | $0.01595 |
| Haiku 4.5 | $0.00002 | $0.00798 |
Grade A, and why
scope 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 1mo 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 — 787 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Command - Prepare Focused Analysis
Prepare a focused analysis scope for large codebases or monorepos using repomix. Creates a digestible snapshot of the target code for subsequent security analysis.
Saved scope files are context artifacts for Claude-side review and threat modeling. Static tool entrypoints like scan_orchestrator.py still run against the original source directory or workspace, not the generated markdown snapshot.
Flags
| Flag | Effect |
|---|---|
--list |
List workspaces/packages in monorepo with size estimates |
--compress |
Use language-aware compression (Go: 97%, TS/JS: 80%) |
--include |
Glob patterns to include |
--exclude |
Glob patterns to exclude |
--name |
Output filename (default: derived from path) |
--force |
Force scope even if >300k tokens |
--language |
Force specific language strategy (go|ts|py|java|rust|php|cs|ruby|sol) |
List Workspaces (--list)
When --list is provided, detect and display monorepo structure:
/vuln-scout:scope --list
Detects:
- npm/yarn/pnpm workspaces (
package.json,pnpm-workspace.yaml) - Go modules (
go.work, multiplego.mod) - Maven/Gradle modules (
pom.xml,settings.gradle) - Rust workspaces (
Cargo.toml) - Python packages (
pyproject.toml,setup.py)
Output:
## Detected Workspaces
| Name | Path | Language | Est. Tokens | Risk |
|------|------|----------|-------------|------|
| query-service | query-service/ | Go | 184k | HIGH |
| index-service | index-service/ | Go | 100k | HIGH |
| tahoma | tahoma/ | Go | 706k | MEDIUM |
### Recommendations
- query-service: `/scope query-service --name qs`
- tahoma is oversized: scope sub-directories individually
Polyglot Monorepo Detection (Automatic)
When --list is used, polyglot detection happens automatically. Mixed-language codebases are identified and services are mapped to their languages:
/vuln-scout:scope --list
Step 1: Detect All Languages
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.
- 1mo ago First seen · 787 lines · 21 tokens per session scan A 1cb9407ada6e
scope is a command published in the GitHub repository allsmog/vuln-scout (25 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 7,976 once invoked, about $0.0001 per session on Opus 5.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
fix
Apply code-level fixes for ALL validated findings, one at a time — modifies the target repository's source code.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
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.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.