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/rules/robertsfeir/atelier-pipeline/dor-dod)<a href="https://agentmods.dev/rules/robertsfeir/atelier-pipeline/dor-dod"><img src="https://agentmods.dev/badge/rules/robertsfeir/atelier-pipeline/dor-dod/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/rules/robertsfeir/atelier-pipeline/dor-dod"><img src="https://agentmods.dev/badge/rules/robertsfeir/atelier-pipeline/dor-dod.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.02260 | $0.02260 |
| Opus 5 | $0.01130 | $0.01130 |
| Sonnet 5 | $0.00452 | $0.00452 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
dor-dod 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 9d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Definition of Ready / Definition of Done
Shared framework for all agents. Replaces procedural checklists with structural output requirements.
How It Works
- DoR = first section of your output. Proves you read upstream artifacts.
- DoD = last section of your output. Proves you covered everything.
- Eva verifies both at phase transitions.
- Poirot independently verifies Colby's DoD against actual code.
Both DoR and DoD are placed inside the <output> tag in agent persona files.
The <output> tag is the structural container for everything an agent produces,
and DoR/DoD are the bookends: DoR opens the output, DoD closes it.
DoR and DoD Inside <output>
When an agent produces output, the DoR section comes first and the DoD section comes last. Everything the agent delivers goes between them. Here is the structural pattern:
<output>
## DoR: Requirements Extracted
**Source:** [paths to upstream artifacts you read]
| # | Requirement | Source | Source citations |
|---|-------------|--------|-----------------|
| 1 | [specific requirement] | [spec section / UX screen / ADR step] | [file:line or section ref] |
| 2 | [specific requirement] | [spec section / UX screen / ADR step] | [file:line or section ref] |
**Retro risks:** [relevant patterns from retro-lessons.md, or "None"]
[... agent's main work output goes here ...]
## DoD: Verification
| # | Requirement | Status | Evidence |
|---|-------------|--------|----------|
| 1 | [from DoR] | Done | [where/how -- file, section, test] |
| 2 | [from DoR] | Deferred | [explicit reason] |
**Grep check:** `TODO/FIXME/HACK/XXX` in output files -> [count]
**Template:** All sections filled -- no TBD, no placeholders
</output>
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.
- 9d ago First seen · 222 lines · 2,260 tokens per session scan A d8e7e0c587c1
dor-dod is a cursor rule published in the GitHub repository robertsfeir/atelier-pipeline (25 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,260 tokens to every session, about $0.0113 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.