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 skills add damusix/atomic-claude --skill atomic-documentationgit clone --depth 1 https://github.com/damusix/atomic-claudeWrote 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/skills/damusix/atomic-claude/atomic-documentation)<a href="https://agentmods.dev/skills/damusix/atomic-claude/atomic-documentation"><img src="https://agentmods.dev/badge/skills/damusix/atomic-claude/atomic-documentation/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/skills/damusix/atomic-claude/atomic-documentation"><img src="https://agentmods.dev/badge/skills/damusix/atomic-claude/atomic-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00169 | $0.02759 |
| Opus 5.5 | $0.00068 | $0.01104 |
| Sonnet 5.5 | $0.00034 | $0.00552 |
| Haiku 4.5 | $0.00017 | $0.00276 |
Grade A, and why
atomic-documentation 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-fires on: "doc this change", "what surfaces does this touch", "doc impact for this diff", "what needs documenting".
Also invoked by /documentation (authoring mode) and by ship verbs (maintenance mode, between stage and signals).
This skill reads the project's indexed documentation surfaces, matches a diff against them, and either flags stale/incomplete docs (maintenance mode) or runs the full discovery + generation pipeline (authoring mode). It emits a structured YAML block listing affected surfaces. When the user picks "Yes", it opens the file and makes the edit.
Two surfaces, one file voice
| Surface | Where | Style |
|---|---|---|
| How Claude talks | TUI replies | Atomic output style: terse, fragments OK, drop articles. Governed by output-styles/atomic.md. |
| How files are written | All file content | The atomic-writing skill, everywhere: README, guides, reference, specs, designs, wiki pages, CLAUDE.md, and the prompt artifacts under commands/, agents/, skills/, rules/. One voice; length is set by what the surface carries. |
There is no separate terse-technical voice. A spec and a README differ in length and structure, not in voice, and either one prefers a diagram over a paragraph when the content has a shape.
How surface routing works
The skill reads the ## Documentation surfaces table from the project's CLAUDE instructions. Search order: claude.local.md or CLAUDE.local.md (treated as a pair) → CLAUDE.md. First file containing the heading wins.
Expected table format:
## Documentation surfaces
| Path | Covers | Voice |
|------|--------|-------|
| `docs/architecture/payments.md` | billing, webhooks, Stripe | atomic-writing |
| `docs/models/README.md` | data model, ERD, migrations | atomic-writing |
| `docs/api/endpoints.md` | REST API, auth, rate limits | atomic-writing |
The Covers column is the matching key. The skill compares diff file paths and changed symbols against these terms to classify each surface as stale, incomplete, or missing. If no ## Documentation surfaces section exists in any of the searched files, the skill returns empty surfaces — clean degradation with no false positives.
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.
- 1mo ago First seen · 209 lines · 169 tokens per session scan A d1a71f593a0a
atomic-documentation is a skill published in the GitHub repository damusix/atomic-claude (113 stars, last pushed today), licensed MIT. It adds 169 tokens to every session and 2,759 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.
Other skills, from other repositories
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
loongsuite-pilot-ops
Skill "loongsuite-pilot-ops" from alibaba/loongsuite-pilot, covering loongsuite-pilot-ops, quick start, todo: add quick start commands and usage.
sipcode-regress
Check the user's own local Claude Code and Codex logs for regressions after an update (prompt-cache misses, 5-minute cache TTL, uncached context, hourly cache rebuilds, Codex usage limit draining faster per token) and pin each one to the version that introduced it, using the Sipcode CLI. Use when the user asks whether…
sipcode-spend
Report how much the user spent on Codex (tokens and cost at API prices) today, this month, the projected month end, or over a period, from their local Codex logs, using the Sipcode CLI. Use when the user asks how much they spent on Codex, how many tokens Codex used today or this month, or what this month will cost.
sipcode-why
Explain why a Codex session used so many tokens (largest requests, files read more than once, context carried while idle) from the user's local Codex logs, using the Sipcode CLI. Use when the user asks why their last Codex session was so expensive, where the tokens went, or what made a session cost so much.
impact
A/B compare the user's actual token spend before and after they installed Sipcode's optimizers — on their own session data. The honesty-first savings verifier. Use when the user asks "is sipcode actually saving me tokens?", "show me the impact", "prove sipcode is working", or any variant of "is this thing worth…