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.
git 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/pipeline)<a href="https://agentmods.dev/commands/robertsfeir/atelier-pipeline/pipeline"><img src="https://agentmods.dev/badge/commands/robertsfeir/atelier-pipeline/pipeline/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/commands/robertsfeir/atelier-pipeline/pipeline"><img src="https://agentmods.dev/badge/commands/robertsfeir/atelier-pipeline/pipeline.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01697 |
| Opus 5 | $0.00012 | $0.00848 |
| Sonnet 5 | $0.00005 | $0.00339 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
pipeline 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 10d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For skill phases (Robert, Sable, Agatha planning), adopt their persona and run in the main thread. For other subagent phases, invoke them with focused prompts and read results.
Eva assesses scope at the start, recommends a sizing, and presents all four options as a choice list. The recommended option is in bold. The user picks.
- Micro -- <=2 files, purely mechanical, no tests needed, no brain
- Small -- single ADR step, <3 files, bug fix. Skip Robert/Sable, auto-advance, pause before commit
- Medium -- 2-4 ADR steps, typical feature. Pause between major phases, auto-advance within
- Large -- 5+ ADR steps, new system, multi-concern. Full ceremony, one phase per turn
Example presentation:
This feature sizes as a typical enhancement. Pick your pipeline sizing:
- Micro
- Small
- Medium (recommended)
- Large
User can override at any point: "upgrade to Large" or "downgrade to Small".
Budget Estimate Gate (after sizing choice, before first agent invocation)
After the user selects sizing, if the sizing triggers the gate (Large always, or
Medium when token_budget_warning_threshold is configured), Eva computes and
displays the budget estimate before invoking the first agent.
See the <gate id="budget-estimate"> section in pipeline-orchestration.md for
the full gate rules table, estimate presentation format, and user cancellation flow.
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.
- 10d ago First seen · 190 lines · 23 tokens per session scan A bf344b94a684
pipeline is a command published in the GitHub repository robertsfeir/atelier-pipeline (25 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,697 once invoked, about $0.0001 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
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.
develop
Implement skill development issues with TDD-governed workflow.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.