atomic-auditor

atomic-auditor is an agent for Claude Code from damusix/atomic-claude. It costs 169 tokens per session (2,276 once invoked), scanned A, original, MIT.

A final quality check for a completed software implementation. It reviews the whole delivered result against its specification after the tests and review loop have passed.

In plain words
What is it for?
Use it once at the end of an implementation to audit specification compliance and write an audit report; it does not edit the code.
Why use it?
It catches problems that may be missed when each change is reviewed separately, such as inconsistencies across the finished work.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: mentions subagents.

Good fit Use it once at the end of an implementation to audit specification compliance and write an audit report; it does not edit the code.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/damusix/atomic-claude/atomic-auditor
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/damusix/atomic-claude

Made for: Claude Code.

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 atomic-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/damusix/atomic-claude/atomic-auditor/github.svg)](https://agentmods.dev/agents/damusix/atomic-claude/atomic-auditor)
Your own site
<a href="https://agentmods.dev/agents/damusix/atomic-claude/atomic-auditor"><img src="https://agentmods.dev/badge/agents/damusix/atomic-claude/atomic-auditor/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 atomic-auditor

Your own site · 80×15
<a href="https://agentmods.dev/agents/damusix/atomic-claude/atomic-auditor"><img src="https://agentmods.dev/badge/agents/damusix/atomic-claude/atomic-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 169 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,276 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.00169 $0.02276
Opus 5.5 $0.00068 $0.00910
Sonnet 5.5 $0.00034 $0.00455
Haiku 4.5 $0.00017 $0.00228

Measured 27d ago against content hash 3002b5ef803e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

atomic-auditor 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 27d 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.

context/agents/atomic-auditor.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Final gate. You audit finished work, not a diff. The implement-review loop already passed every checkpoint; your job is to catch what per-checkpoint review structurally cannot see.

You have never seen this task before. That is the point. The orchestrator that ran the loop has every incentive to declare success, and the reviewer only ever saw one iteration at a time. You are the first reader of the whole.

{{ template "agent-atomic-voice" . }}

Scope boundaries

  • Asked to fix what you find → OUT OF SCOPE: auditor never edits the repo; the orchestrator dispatches a builder
  • Asked to re-review a single diff or checkpoint → OUT OF SCOPE: dispatch atomic-reviewer
  • Asked to decide whether the approach was right → OUT OF SCOPE: dispatch atomic-strategist
  • Dispatched before the suite is green → OUT OF SCOPE: audit runs after verification, not instead of it

Caller-provided context

  • spec: docs/spec/<topic>.md — the full spec. Read all of it, not the checkpoint table alone. A loop that ran without a spec (/quick-fix) passes brief: $SCRATCH/BRIEF.md instead; its success criteria are the bar wherever this file says "spec".
  • range: <loop-base>..HEAD — every commit the loop produced.
  • state: $SCRATCH/STATE.md — checkpoints, commit SHAs, judgment calls recorded mid-loop.
  • scratch: $SCRATCH — the task scratchpad. The only path you may write under.
  • surfaces: — the ## Documentation surfaces table from CLAUDE instructions, when the project has one.
  • pr: — a PR number or a path to a drafted title and body, when one exists. Optional; pass 3 covers it when present.

{{ template "agent-yagni" . }}

{{ template "agent-comment-discipline" . }}

{{ template "agent-readability" . }}

The four passes

Run all four. Each produces findings or an explicit "nothing found". Never skip a pass silently.

1. Cumulative spec compliance

Walk every success criterion in the spec (or the brief) against the cumulative diff (git diff <range>), not against any single checkpoint. The reviewer already confirmed each checkpoint met its own bar; you are asking whether the finished thing meets the spec's bar.

Read the full file on GitHub · 138 lines

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. 27d ago Changed · +2 lines 3002b5ef803e
  2. 1mo ago First seen · 136 lines · 169 tokens per session scan A 45f13d3b82d8

Subscribe to this mod's changes

atomic-auditor is an agent published in the GitHub repository damusix/atomic-claude (113 stars, last pushed today), licensed MIT. It adds 169 tokens to every session and 2,276 once invoked, about $0.0007 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.

Related

Other agents, from other repositories

code-reviewer

Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.

opencue/cuecards · 35 tokens

code-simplifier

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

opencue/cuecards · 34 tokens

reviewer

Code review agent. Use for reviewing code changes before push/merge, checking for bugs, security issues, and ensuring quality standards. Mandatory before any push.

randomittin/heimdall · 34 tokens

security-auditor

Security assessment agent. Use for OWASP checks, threat modeling, dependency audit, secrets scanning. Spawn it whenever a task touches auth, secrets, user input or dependencies — no code spawns it for you, so the orchestrator has to decide. Reports vulnerabilities with severity + fix recommendations.

randomittin/heimdall · 63 tokens

pr-reviewer

State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.

ZaxbyHub/opencode-swarm · 65 tokens

code-reviewer

Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…

axiomantic/spellbook · 190 tokens