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 skills/damusix/atomic-claude/atomic-writingnpx skills add damusix/atomic-claude --skill atomic-writinggit 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-writing)<a href="https://agentmods.dev/skills/damusix/atomic-claude/atomic-writing"><img src="https://agentmods.dev/badge/skills/damusix/atomic-claude/atomic-writing.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00268 | $0.05359 |
| Opus 5 | $0.00134 | $0.02679 |
| Sonnet 5 | $0.00054 | $0.01072 |
| Haiku 4.5 | $0.00027 | $0.00536 |
Grade A, and why
atomic-writing 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 5d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- "draft the README", "write the docs", "improve this prose", "edit the guide"
- "write the spec", "write the design doc", "clean up this doc", "make this readable"
- "clean this up", "tighten this", "edit for tone" — on any file the repo ships
/documentationediting any indexed surface- Writing or editing any
.mdfile that ships in the repo
Every file this repo ships has one voice: plain, specific, technical, and visual where the content has a shape. A spec, a README, a design doc, and a command artifact differ in length and structure. They do not differ in voice.
The reason is a contract that reads well to only one party is broken. A spec an agent can walk but a human cannot review is not a contract, and a guide a human enjoys but an agent cannot follow is not documentation. Write for the human. A model reads what a human reads.
<voice_rules>
The one boundary
| Atomic output style | Atomic-writing (this skill) | |
|---|---|---|
| Governs | How Claude talks in the terminal | What Claude writes into files |
| Where | TUI replies to the user | Every .md file that ships in the repo |
| Form | Fragments OK, drop articles, ASCII only | Full sentences where prose is right, Mermaid where a picture is right |
| Lives in | output-styles/atomic.md |
This skill |
Nothing else splits. There is no separate "terse technical" voice for specs, designs, CLAUDE.md, or agent prompts.
Same voice, different length
Length is set by the job the surface does, not by a compression quota and not by a house maximum.
| Surface | Job | Length |
|---|---|---|
README.md, docs/guides/ |
Teach the system to someone new | As long as the explanation needs |
docs/reference/ |
Answer a lookup fast | Tables and lists first, prose for what a table cannot hold |
docs/spec/, docs/design/ |
Carry a contract a human approves and an agent implements | Shortest that carries the contract in full; the structure is the contract |
docs/wiki/ |
Orient a reader to a codebase | Dense. Facts with paths, no throat-clearing |
docs/research/ |
Record what was found and why a path was chosen | As long as the evidence needs |
CLAUDE.md, rules/ |
Instruct, in every session | Tightest. Every line costs tokens on every turn |
commands/, agents/, skills/, output-styles/ |
Instruct an agent mid-task | Tight. Instruct plainly, cut rationale that only defends the instruction |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 273 lines · 268 tokens per session scan A 1b50a8037044
atomic-writing is a skill published in the GitHub repository damusix/atomic-claude (84 stars, last pushed today), licensed MIT. It adds 268 tokens to every session and 5,359 once invoked, about $0.0013 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 skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
gitnexus
将 GitNexus 作为受控可选代码智能能力接入，用于 brownfield MCP 查询、影响面分析、 detectchanges、多仓分析和更深代码图谱证据。输出必须回落到 /team- 主链和 artifacts。.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.