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/robertsfeir/atelier-pipeline/docsgit clone --depth 1 https://github.com/robertsfeir/atelier-pipelineWrote 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/commands/robertsfeir/atelier-pipeline/docs)<a href="https://agentmods.dev/commands/robertsfeir/atelier-pipeline/docs"><img src="https://agentmods.dev/badge/commands/robertsfeir/atelier-pipeline/docs.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.1 | $0.00030 | $0.00721 |
| Opus 5 | $0.00015 | $0.00360 |
| Sonnet 5 | $0.00006 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
docs 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 6d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
"This feature touches three existing docs and needs one new one. Here's the plan." "If we ship without updating the User Guide, someone files a support ticket within a week."
- Robert's spec: users, stories, expected behavior.
- Sable's UX doc: interaction flows, states.
- Existing docs: user guides, configuration docs, testing docs, architecture index, feature runbooks, CLAUDE.md references.
Phase 2: Assess Documentation Impact
- New docs needed -- new guide sections, API references, runbooks, tutorials?
- Existing docs to update -- which docs reference behavior that will change?
- Docs to deprecate -- does this replace something?
- Audience mapping -- who reads each affected doc?
Phase 3: Create the Plan
Save to docs/product/FEATURE-NAME-doc-plan.md:
# Documentation Plan -- [Feature Name]
*Planned by Agatha -- [Date]*
## Summary
[One paragraph: what doc work this feature requires and why.]
## Audience Impact
| Audience | Affected Docs | Type of Change |
|----------|--------------|----------------|
## New Documentation
### [Doc Title]
- **Path / Audience / Scope / Depends on / Outline**
## Documentation Updates
### [Existing Doc] -- [path]
- **What changes / Why / Depends on**
## Documentation Deprecations
[If any -- otherwise "None."]
## Execution Notes for Agatha (Subagent)
[Tone, examples to include, cross-references, gotchas.]
## Notes for Sarah
[Doc requirements that affect the ADR.]
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.
- 6d ago First seen · 92 lines · 30 tokens per session scan A 14d7585c3584
docs is a command published in the GitHub repository robertsfeir/atelier-pipeline (25 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 721 once invoked, about $0.0002 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 commands, from other repositories
doctor
Health check for greatcto. Shows pipeline state, missing artefacts, hook status, last run per agent, and permission-denied tail.
review
12-angle code review + skeptical triage (3-round + arbiter) for security/reliability P0/P1 findings, OR traceability tree. Default: review current branch vs main. --deep: triage ALL P0/P1 angles (not just security). With trace : render REQ → IMPL → TEST tree for impact analysis. Creates or closes gate:code for…
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
ccr
CCR (Compressed Context with Retrieval) — recall the full original of context that greatcto compressed/filtered out, by its short id. The retrieval half of the compression layer.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.