auditor:spec-audit

auditor:spec-audit is a command for Claude Code from solanabr/auditor-skill. It costs 35 tokens per session (237 once invoked), scanned A, original, MIT.

A comparison between a written technical specification and the code that implements it. A specification may be a design document, whitepaper, or RFC describing required behavior.

In plain words
What is it for?
Use it to extract requirements, match them to source code, and produce a compliance table with code locations and findings.
Why use it?
It reveals requirements the code does not meet, behavior the specification does not describe, and requirements that were never implemented.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the auditor plugin — 1 skill, 17 commands, 9 agents shipped together

Good fit Use it to extract requirements, match them to source code, and produce a compliance table with code locations and findings.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/solanabr/auditor-skill/spec-audit
Install

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.

Clone the repo
git clone --depth 1 https://github.com/solanabr/auditor-skill

Made for: Claude Code.

Or install auditor, the plugin that ships this one along with the rest of its 1 skill, 17 commands, 9 agents.

Wrote 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.

agentmods badge for auditor:spec-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/solanabr/auditor-skill/spec-audit/github.svg)](https://agentmods.dev/commands/solanabr/auditor-skill/spec-audit)
Your own site
<a href="https://agentmods.dev/commands/solanabr/auditor-skill/spec-audit"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/spec-audit/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.

agentmods 80×15 button for auditor:spec-audit

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 237 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00237
Opus 5.5 $0.00014 $0.00095
Sonnet 5.5 $0.00007 $0.00047
Haiku 4.5 $0.00003 $0.00024

Measured 1mo ago against content hash f7c5a7331203, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

commands/spec-audit.md · 17 lines

What it actually says

auditor-skill — Spec Compliance (Mode 5)

Arguments: $ARGUMENTS

  1. Extract a requirement list (Spec-IR) from the supplied spec.
  2. Run Phase 0 setup + Phase 0.5 Context Reconstruction; map each instruction / state field to the spec's stated behavior.
  3. Build a Compliance Matrix: each requirement → [MET] / [VIOLATED-N] / [UNIMPLEMENTED] / [UNDOCUMENTED-BEHAVIOR], cited to code L#.
  4. 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.
  5. Report the Compliance Matrix + findings.
Changes

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.

  1. 1mo ago First seen · 17 lines · 35 tokens per session scan A f7c5a7331203

Subscribe to this mod's changes

auditor:spec-audit is a command published in the GitHub repository solanabr/auditor-skill (61 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 237 once invoked, about $0.0001 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.