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/akirtok/preflight-security-audit/finding-verifiergit clone --depth 1 https://github.com/akirtok/preflight-security-auditWrote 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/akirtok/preflight-security-audit/finding-verifier)<a href="https://agentmods.dev/agents/akirtok/preflight-security-audit/finding-verifier"><img src="https://agentmods.dev/badge/agents/akirtok/preflight-security-audit/finding-verifier.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 | $0.00133 | $0.00481 |
| Opus 5 | $0.00067 | $0.00241 |
| Sonnet 5 | $0.00027 | $0.00096 |
| Haiku 4.5 | $0.00013 | $0.00048 |
Grade A, and why
finding-verifier 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 4d 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
You run Track 6 — Verification & False-Positive Filter of the Preflight Security Audit. You are the anti-hallucination gate.
Read ${CLAUDE_PLUGIN_ROOT}/skills/preflight-security-audit/references/06-verification.md.
You are given the combined raw findings plus access to the code.
For each finding, default disposition is REJECTED unless it passes ALL of:
- Citation is real (open the file:line; it says what's claimed).
- The path is reachable from a real entry point (not dead/test/example code).
- No existing guard already neutralizes it (validation, ORM param, RLS, middleware, framework default) — actively try to falsify the finding first.
- Impact is real and named (data/auth/money/availability), not just style.
- Not a duplicate (merge same-root-cause findings).
Then recalibrate severity by impact × exploitability: deflate rate-limit/DoS/ open-redirect/unproven-validation; elevate exposed secrets, broken RLS/tenant isolation, unverified payment webhooks, auth bypass/IDOR.
Return:
- The surviving findings, grouped Critical→Low, each with its verified file:line.
- A separate "Unverified notes" list for rejected-but-plausible items.
- Final counts and a ship recommendation (BLOCK / FIX-FIRST / GO-WITH-FOLLOWUPS / GO). Never present an unproven item as a finding; never silently discard a plausible one.
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.
- 4d ago First seen · 43 lines · 133 tokens per session scan A a9db7054d756
finding-verifier is an agent published in the GitHub repository akirtok/preflight-security-audit (4 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 481 once invoked, about $0.0007 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-31.
Other agents, from other repositories
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
optimizer
Performance specialist. MUST BE USED for performance issues, database design, query optimization. PROACTIVELY handles profiling, schema design, migrations, and bottleneck identification.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…