documentation

A command for creating and maintaining a project’s documentation index. It finds documentation files, records what each one covers in CLAUDE.md, and checks whether changed or missing documentation needs attention.

In plain words
What is it for?
Use it to bootstrap documentation tracking, discover newly added docs, review docs affected by a Git range, or preview the findings with a dry run.
Why use it?
It helps teams see where project information is documented and notice when the relevant documents are missing, stale, or incomplete. This reduces the need to search through the repository manually.

Command

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.

agentmods
npx agentmods add commands/damusix/atomic-claude/documentation
Clone the repo
git clone --depth 1 https://github.com/damusix/atomic-claude
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,021 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00057 $0.03021
Opus 5 $0.00028 $0.01510
Sonnet 5 $0.00011 $0.00604
Haiku 4.5 $0.00006 $0.00302

Measured 2d ago against content hash f8a0d94fbb03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

context/commands/documentation.md · 330 lines

How it starts

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

Run /documentation to bootstrap doc surface indexing or perform a full documentation pass.

Flags

  • --print-template — print the ## Documentation surfaces table skeleton to stdout and exit. Paste into your CLAUDE.md to declare custom surfaces manually.
  • --dry-run — print discovered/stale surfaces without applying edits or staging anything.
  • --discover — re-scan and offer to update the surfaces table even when a table already exists. Use after adding new doc files.
  • <range> — any valid git range (HEAD~5..HEAD, main..feature-branch). If omitted, defaults to <base>..HEAD where <base> is the merge-base with main.

Step 0 — Handle flags

If --print-template is present, print the following and exit:

## 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 |
| `README.md` | project overview, quick start | atomic-writing |

Add this section to your committed CLAUDE.md and fill in your project's doc files. Voice is always atomic-writing — the column exists to name the skill that governs the edit, not to pick between alternatives.

Step 1 — Detect mode

Check whether a ## Documentation surfaces table exists in the project's committed CLAUDE.md (search CLAUDE.md at the git root; also check claude.local.md / CLAUDE.local.md).

  • Table absent OR --discover flag present → run bootstrap mode (Step 2).
  • Table present AND no --discover flag → run authoring mode (Step 5).

Step 2 — Bootstrap: scan doc files

Run the deterministic scan:

atomic docs scan 2>/dev/null

If atomic is absent or returns a non-zero exit, fall back to:

find docs/ doc/ documentation/ wiki/ ADR/ adr/ decisions/ -name '*.md' 2>/dev/null
find . -maxdepth 3 -name 'README.md' 2>/dev/null | grep -v node_modules | grep -v .git

Read the full file on GitHub · 330 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. 2d ago First seen · 330 lines · 0 tokens per session scan A f8a0d94fbb03

Subscribe to this mod's changes

documentation is a command published in the GitHub repository damusix/atomic-claude (83 stars, last pushed 8d ago), licensed MIT. It adds 57 tokens to every session and 3,021 once invoked, about $0.0003 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.