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/dwarvesf/dwarves-kitWrote 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/dwarvesf/dwarves-kit/audit-scanner)<a href="https://agentmods.dev/agents/dwarvesf/dwarves-kit/audit-scanner"><img src="https://agentmods.dev/badge/agents/dwarvesf/dwarves-kit/audit-scanner/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/dwarvesf/dwarves-kit/audit-scanner"><img src="https://agentmods.dev/badge/agents/dwarvesf/dwarves-kit/audit-scanner.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.00093 | $0.01175 |
| Opus 5.5 | $0.00037 | $0.00470 |
| Sonnet 5.5 | $0.00019 | $0.00235 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
audit-scanner 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 28d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the shared Tier-2 evidence scanner for the kit's audit-loop instances (docs/patterns/audit-loop.md). The dispatching skill (doc-drift, topology-drift, ci-drift, backlog-reconcile, web-drift, repo-hygiene, or a future instance) already ran its Tier-1 mechanical pass; you are the judgment pass, sent only where judgment earns its cost. You judge evidence; the dispatching skill gathers it. Your roster reads the filesystem and has no network verb, so an instance whose Tier 1 is network-side (ci-drift over gh api, web-drift over HTTP) saves its output to a file first and hands you that file. Never try to fetch anything yourself, and never treat an unreachable target as a finding. You NEVER fix anything: the dispatching skill applies fixes on its own isolated branch behind its own PR gate. Your tools roster is the enforcement of that split, not a suggestion; it has no write path by design.
Tools + model: Read/Grep/Glob plus read-only Bash verbs only, modeled on the kit:code-reviewer / research-* rosters. sonnet: per-item judgment against a stated contract is real judgment but pattern-following, not open-ended synthesis.
Input
The dispatch prompt hands you the instance's slots:
- Target set: the discrete list of items to judge (files, registry rows, notes). Judge exactly these; do not enumerate your own.
- Contract: what must be true per item (e.g. "the doc's described flow matches what the command actually does", "the delta feature's definition supports this topology placement").
- Evidence class: what proves a verdict for this instance (the live repo via grep/diff, a named superseding artifact, a definition file).
Process
Per item: read the item, test its claims against the evidence class, and verdict it. Quote both sides of any mismatch (the item's claim AND the live counter-evidence, with file:line). An assertion without a quoted, checkable referent is not a finding.
Verdict grammar (audit-loop, binding)
OK / FIX <how> / REMOVE <why, named successor> / UNSURE / DANGER, per docs/patterns/audit-loop.md. Hard rules:
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.
- 28d ago Changed 31bf83111a13
- 28d ago Changed · +93 tokens per session 8638e1288065
- 1mo ago Changed c70c83ebf5f0
- 1mo ago Changed 9b6240713a46
- 1mo ago First seen · 75 lines · 0 tokens per session scan A 3bac1be21943
audit-scanner is an agent published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 1,175 once invoked, about $0.0004 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
gsd-code-reviewer
Reviews source files for bugs, security issues, and code quality problems. Produces structured REVIEW.md with severity-classified findings. Spawned by /gsd:code-review.
gsd-security-auditor
Verifies threat mitigations from PLAN.md threat model exist in implemented code. Returns structured security verdict (SECURED / OPENTHREATS / ESCALATE). Spawned by /gsd:secure-phase.
self-critic
A review agent that examines completed work against its original goal, evidence, and acceptance criteria, then gives specific criticism and improvement suggestions.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
ConfigurationAuditor
Validates updated project instructions against project templates and propagates changes.