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.
npx skills add allsmog/vuln-scout --skill review-prgit 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/skills/allsmog/vuln-scout/review-pr)<a href="https://agentmods.dev/skills/allsmog/vuln-scout/review-pr"><img src="https://agentmods.dev/badge/skills/allsmog/vuln-scout/review-pr/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/skills/allsmog/vuln-scout/review-pr"><img src="https://agentmods.dev/badge/skills/allsmog/vuln-scout/review-pr.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.00016 | $0.00293 |
| Opus 5 | $0.00008 | $0.00147 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
review-pr 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 11d 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.
What it actually says
Review PR
Use this task skill when the user asks to review this PR, scan a PR, run a diff scan, or check a pull request for vulnerabilities.
Workflow
- Identify the base ref, defaulting to
origin/mainwhen the user does not specify one. - Run
/vuln-scout:diff <base>to produce changed-code findings. - Call
code-revieweron new or changed findings only. - Run
/vuln-scout:verify --from .claude/diff-findings.jsonfor findings that affect the PR. - Call
false-positive-verifierfor high-impact or ambiguous results. - Trigger
poc-safety-checkbefore any dynamic validation or PoC work. - Render
/vuln-scout:report --format mdfor the PR comment payload. - Optionally render
/vuln-scout:report --format bundle --output evidence-bundlefor evidence handoff.
Produces
.claude/diff-findings.jsonpr-comment.md- optional
evidence-bundle/
When NOT To Trigger
Do not trigger for general git diff questions, style-only code review, STRIDE threat modeling, or framework-specific vulnerability education without a PR review request.
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.
- 11d ago First seen · 30 lines · 16 tokens per session scan A e8d4996509d2
review-pr is a skill published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 293 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 skills, from other repositories
sast-semgrep
Static application security testing (SAST) using Semgrep for vulnerability detection, security code review, and secure coding guidance with OWASP and CWE framework mapping. Use when: (1) Scanning code for security vulnerabilities across multiple languages, (2) Performing security code reviews with pattern-based…
sast-semgrep
Static application security testing (SAST) using Semgrep for vulnerability detection, security code review, and secure coding guidance with OWASP and CWE framework mapping. Use when: (1) Scanning code for security vulnerabilities across multiple languages, (2) Performing security code reviews with pattern-based…
secure-code-review
Performs a structured security code review against OWASP ASVS 4.0.3 verification requirements and CWE Top 25. Auto-invoked on pull request reviews, when code touching authentication, authorization, cryptography, or input handling is shared. Produces findings mapped to ASVS controls and CWE identifiers with severity…
sast-config
Reviews and tunes SAST tool configurations against OWASP ASVS 4.0.3 and CWE Top 25. Auto-invoked when reviewing Semgrep rules, CodeQL queries, SAST CI integration, or false positive triage workflows. Produces a SAST maturity assessment covering rule authoring, severity tuning, custom rule development, and CI…
crypto-source-audit
Audits cryptographic source code for timing side channels, missing secret zeroization, non-constant-time comparison, and weak randomness. Use when reviewing crypto primitives, key/nonce/PSK handling, TLS or handshake code, signature or KEM implementations, or any function that touches secret key material, including…
security-code-review
Full security code review with Semgrep Pro scan, taint analysis, CWE mapping, OWASP Top 10 coverage, and generation of a formal Security Code Review Report saved to /security-review/ in the repository root. Use when reviewing code for vulnerabilities, auditing a file for security issues, or before merging…