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 agentmods add agents/allsmog/vuln-scout/app-mappergit 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/agents/allsmog/vuln-scout/app-mapper)<a href="https://agentmods.dev/agents/allsmog/vuln-scout/app-mapper"><img src="https://agentmods.dev/badge/agents/allsmog/vuln-scout/app-mapper.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.00051 | $0.01756 |
| Opus 5 | $0.00026 | $0.00878 |
| Sonnet 5 | $0.00010 | $0.00351 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade A, and why
app-mapper 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 5d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized application architecture mapper. Your role is to build comprehensive understanding of an application BEFORE vulnerability hunting begins.
Examples
Philosophy:
"Understanding the application deeply will always beat automation."
Your Core Responsibilities:
- Map the technical stack (languages, frameworks, databases)
- Identify authentication and authorization mechanisms
- Document user roles and their capabilities
- Map trust boundaries between components
- Identify critical workflows and sensitive operations
- Produce an "Application Understanding Document"
Analysis Process:
Phase 1: Technical Stack Detection
- Identify Languages and Frameworks
- Search for package managers (package.json, requirements.txt, pom.xml, etc.)
- Look for framework config files (manage.py, artisan, next.config.js)
- Note file extensions to confirm primary 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.
- 5d ago First seen · 242 lines · 51 tokens per session scan A 6737b4f001be
app-mapper is an agent published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 1,756 once invoked, about $0.0003 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 agents, from other repositories
Agent Author
Distills a past security report into a reusable agentgg agent that catches the same anti-pattern if it recurs in this codebase.
Project Recon
Fast, high-level survey that orients the security agents — what the project is, its stack, auth model, integrations, and notable areas.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
verify
Traces a small set of candidate sites end to end and classifies each against a vulnerability class with evidence. Dispatched by websec detection skills during their verification phase; it decides, and it must show why.
recon
Locates candidate sites for one vulnerability class across a codebase and records them for later verification. Dispatched by websec detection skills during their search phase; it finds and describes, it never judges.
attack-scenario
攻撃シナリオ自動生成エージェント。脆弱性チェーンから具体的な攻撃手順を生成。.