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 commands/damusix/atomic-claude/example-onlygit 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.00000 | $0.00040 |
| Opus 5 | $0.00000 | $0.00020 |
| Sonnet 5 | $0.00000 | $0.00008 |
| Haiku 4.5 | $0.00000 | $0.00004 |
Grade A, and why
example-only 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.
What it actually says
example-only
This command documents how to dispatch. Example only:
Use the agent tool with:
- subagent_type: "atomic-ghost"
No actual dispatch in prose.
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 · 11 lines · 0 tokens per session scan A bee8c2c4799f
example-only is a command published in the GitHub repository damusix/atomic-claude (83 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 40 tokens. 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 commands, from other repositories
develop-configure
The develop orchestrator body: phases, dispatch discipline, quality gates, ceremony lock, ledger, and handoff. Loaded by the develop skill once the operator has chosen a ceremony path.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
add-skill
Add a new Skill to the current plugin with proper structure.
specmanager-design
Design the actual screens for a SpecManager feature as stacked high-fi HTML mockups via the designer subagent. Optional — Plan can run without one, but if a draft exists, Plan refuses to open until it's approved.
specmanager-plan
Draft the execution Plan AND emit task records for a SpecManager feature via the planner subagent. Plans are organised into phases with Fibonacci-scored tasks ≤3.
_subagent-discovery
Whenever a command needs to pick a subagent for a task (planning, task generation, or implementation execution). Do not hardcode agent names in command templates. Do not assume a specific agent exists.