Borrowing it
Nothing to install: this file belongs to allsmog/vuln-scout. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/allsmog/vuln-scout/main/AGENTS.mdgit 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/instructions/allsmog/vuln-scout/agents-md)<a href="https://agentmods.dev/instructions/allsmog/vuln-scout/agents-md"><img src="https://agentmods.dev/badge/instructions/allsmog/vuln-scout/agents-md.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.00518 | $0.00518 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
vuln-scout AGENTS.md 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 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.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VulnScout - Development Guide
Primary runtime target: a Claude Code plugin for whitebox penetration testing, supporting 9 languages including Solidity smart contracts. Codex usage in this repository is for development workflow only, not a separate packaged plugin format.
Project Structure
vuln-scout/
├── .claude-plugin/plugin.json # Plugin manifest
├── agents/ # Autonomous security analysts
├── commands/ # Slash commands (/full-audit, /scope, etc.)
├── hooks/ # Background automation
├── skills/ # Auto-activated knowledge modules
├── references/ # Shared artifact schemas and examples
└── scripts/ # Helper scripts (Joern queries, artifact tooling)
Key Commands
/vuln-scout:full-audit- Main entry point for security audits/vuln-scout:scope- Handle large codebases with compression/vuln-scout:threats- STRIDE threat modeling/vuln-scout:sinks- Find dangerous functions/vuln-scout:verify- CPG-based false positive verification
Development Notes
- Skills are in
skills/with aSKILL.mdand optionalreferences/folder - Agents are markdown files in
agents/with frontmatter - Commands are markdown files in
commands/with YAML frontmatter - Hooks are in
hooks/for event-driven automation - Shared findings contract lives in
vuln-scout/references/findings.schema.json - Prompt-first orchestration artifacts live in
.claude/audit-plan.mdand.claude/review-ledger.json - Prompt eval definitions live in
vuln-scout/evals/; validate withpython3 vuln-scout/scripts/validate_evals.py - Use
kind: findingfor reportable issues andkind: hotspotfor sink-only or framework-pivot leads python3 vuln-scout/scripts/check_consistency.pyis the release gate for doc/schema drift
Supported Languages
Go, TypeScript/JS, Python, Java, Rust, PHP, C#/.NET, Ruby, Solidity
External Tools
- Semgrep - Fast pattern matching
- Joern - Code Property Graph analysis
- Slither - Solidity static analysis
- repomix - Codebase compression for large repos
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 · 48 lines · 518 tokens per session scan A 4445d1ec148d
vuln-scout AGENTS.md is an instructions file published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 2mo ago), licensed MIT. It adds 518 tokens to every session, about $0.0026 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.