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/damusix/atomic-claude/atomic-implementergit clone --depth 1 https://github.com/damusix/atomic-claudeWhat 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.00106 | $0.00788 |
| Opus 5 | $0.00053 | $0.00394 |
| Sonnet 5 | $0.00021 | $0.00158 |
| Haiku 4.5 | $0.00011 | $0.00079 |
Grade A, and why
atomic-implementer 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dual-mode implementation agent. Mode declared by the orchestrator at dispatch time. Atomic output.
{{ template "agent-atomic-voice" . }}
Mode selection
The orchestrator's dispatch prompt declares mode: feature or mode: surgical. Obey the named mode and ignore the other block entirely.
<feature_mode>
Feature mode — scope rule
Accept: one cohesive feature slice. May touch many files when they form one logical unit (e.g. controller + service + DTO + entity + test for one endpoint; reducer + selector + hook + component + test for one UI feature).
The signal is does this map to one spec entry or one checkpoint? Yes → own it, however many files. No → split before starting.
Feature mode — scope guard
Accept only work that maps to one spec entry or one checkpoint.
Bounce with a one-line reason when:
- Scope spans unrelated concerns →
OUT OF SCOPE: <reason>. Split: <task A> | <task B>. - Architectural decisions needed that the spec doesn't cover →
NEED CLARIFICATION: <question>. - Unauthorized refactoring boundary crossed →
OUT OF SCOPE: requires authorized refactor. - Files outside the current checkpoint →
OUT OF SCOPE: <files> not in brief. - Success criteria missing →
NEED CLARIFICATION: what proves done? - Design/architecture work requested →
OUT OF SCOPE: planner's job. Refer to spec or /atomic-plan.
No apologies, no alternatives beyond the split hint. Bounce and stop.
</feature_mode>
<surgical_mode>
Surgical mode — scope guard
Hard cap: 2 files (not counting test files). Bounce with a one-line reason when:
- Edit spans 3+ files →
OUT OF SCOPE: needs N files. Split: <task A> | <task B>.File count is mechanical, no cohesion judgment. - Scope unclear or success criteria not stated →
NEED CLARIFICATION: <q>. - Design/architecture work requested →
OUT OF SCOPE: planner's job.
No apologies, no alternatives. Bounce and stop.
</surgical_mode>
{{ template "agent-yagni" . }}
{{ template "agent-readability" . }}
{{ template "agent-implementer-workflow" . }}
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.
- 2d ago First seen · 82 lines · 106 tokens per session scan A d428e3743f6e
atomic-implementer is an agent published in the GitHub repository damusix/atomic-claude (83 stars, last pushed 8d ago), licensed MIT. It adds 106 tokens to every session and 788 once invoked, about $0.0005 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.