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 commands/solanabr/auditor-skill/spec-auditgit clone --depth 1 https://github.com/solanabr/auditor-skillWrote 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/commands/solanabr/auditor-skill/spec-audit)<a href="https://agentmods.dev/commands/solanabr/auditor-skill/spec-audit"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/spec-audit.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.00035 | $0.00237 |
| Opus 5 | $0.00017 | $0.00118 |
| Sonnet 5 | $0.00007 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
auditor:spec-audit 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.
What it actually says
auditor-skill — Spec Compliance (Mode 5)
Arguments: $ARGUMENTS
- Extract a requirement list (Spec-IR) from the supplied spec.
- Run Phase 0 setup + Phase 0.5 Context Reconstruction; map each instruction / state field to the spec's stated behavior.
- Build a Compliance Matrix: each requirement →
[MET]/[VIOLATED-N]/[UNIMPLEMENTED]/[UNDOCUMENTED-BEHAVIOR], cited to codeL#. - Any
[VIOLATED-N]with N≥6 must pass the Rule 5b gate.[UNDOCUMENTED-BEHAVIOR](code does something the spec never authorizes) is itself a finding. - Report the Compliance Matrix + findings.
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 · 17 lines · 35 tokens per session scan A f7c5a7331203
auditor:spec-audit is a command published in the GitHub repository solanabr/auditor-skill (52 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 237 once invoked, about $0.0002 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 commands, from other repositories
review
Review code changes for Shannon-specific patterns, security, and common mistakes.
debug
Systematically debug errors using context analysis and structured recovery.
pr
Create a PR to main branch using conventional commit style for the title.
plamen-l1
Launch or resume a Plamen L1 infrastructure audit through the deterministic driver.
audit
Full project audit with Health Score, findings, and a prioritized fix plan.
build-unity
Build Unity project (WebGL, Desktop, or PSG1).