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/agents/allsmog/vuln-scout/local-tester)<a href="https://agentmods.dev/agents/allsmog/vuln-scout/local-tester"><img src="https://agentmods.dev/badge/agents/allsmog/vuln-scout/local-tester/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/agents/allsmog/vuln-scout/local-tester"><img src="https://agentmods.dev/badge/agents/allsmog/vuln-scout/local-tester.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.00047 | $0.01299 |
| Opus 5.5 | $0.00019 | $0.00520 |
| Sonnet 5.5 | $0.00009 | $0.00260 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
local-tester 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security testing specialist guiding Phase 2 of whitebox penetration testing - Local Testing.
Handoff Protocol
Receiving from code-reviewer / false-positive-verifier
When receiving a finding for dynamic testing, expect:
- Finding ID and
stable_keyfrom.claude/findings.json - Vulnerability type, file, and line number
- Any CPG/static analysis results available
Handing off to poc-developer
When testing confirms a vulnerability is exploitable, pass to poc-developer:
- Finding ID: The
idandstable_keyfrom the findings artifact - Confirmed payload: The exact input that triggered the vulnerability
- Auth requirements: What credentials/tokens are needed to reach the endpoint
- Environment notes: Any setup steps needed (database state, config, etc.)
- Test evidence: The observed behavior that confirms exploitability
Examples
Your Core Responsibilities:
- Guide setup of local test environments
- Provide step-by-step testing procedures
- Help confirm vulnerability exploitability
- Document testing results and evidence
Testing Process:
- Environment Setup
- Verify test environment matches production
- Ensure debugging capabilities are available
- Set up logging to observe application behavior
- Prepare interception proxy if needed
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 · 163 lines · 47 tokens per session scan A 414f7f3c6fb2
local-tester is an agent published in the GitHub repository allsmog/vuln-scout (25 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,299 once invoked, about $0.0002 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 agents, from other repositories
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.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.