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 rules/nerds-odd-e/doughnut/planninggit clone --depth 1 https://github.com/nerds-odd-e/doughnutWhat 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.02170 | $0.02170 |
| Opus 5 | $0.01085 | $0.01085 |
| Sonnet 5 | $0.00434 | $0.00434 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
planning 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Principles for Slice Delivery
Hard rule for every plan (local or GSD): each slice is either Behavior or Structure, stop-safe, and delivers one observable behavior (or one structure change that enables only the immediate next behavior). GSD phase is a roadmap capability (.planning/phases/NN-slug/). Slice grammar is mandatory.
Vocabulary
| Term | Owner | Meaning |
|---|---|---|
| Milestone | GSD | Versioned increment |
| Phase | GSD | Roadmap capability. ### Phase N:, .planning/phases/NN-slug/ |
| Plan | Shared | One PLAN.md (roadmap phase or .planning/quick/) |
| Slice | Local | One Behavior or one Structure. Stop-safe wrap-up grain |
Behavior and Structure distinction
Behavior (external behavior) has 3 parts: pre-condition, trigger, and post-condition. Each part is:
- externally observable
- of user value
- typically involves state change.
Structure (internal structure) is how code is organized. We want structure to be cohesive, mapped to the domain, and exposing as little information as possible from each module.
Slice principles
Every slice is one of two types:
| Type | What it does | Constraint |
|---|---|---|
| Behavior | Delivers user value directly observable from the external perspective. | Must be externally observable and testable. One observable behavior per slice. |
| Structure | Restructures internals to prepare for the immediate next behavior slice, without changing any external behavior. | All changes must be verifiable from the external perspective (existing tests still pass, no observable difference). No speculative prep for slices beyond the next behavior slice. |
Sequencing rules
- Stop-safe ordering — The user may decide to stop after any slice. The value delivered must be proportional to (or greater than) the number of completed slices, with close to zero waste if remaining slices are never implemented.
- Order by value — Earlier slices = higher user value and usability first.
- Many slices are good — Split as finely as you can while each slice still meets the type constraints above.
- Structure slices only justify themselves through the next behavior slice — A structure slice that is not immediately followed by the behavior slice it enables is speculative waste.
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 · 136 lines · 2,170 tokens per session scan A c751f0148430
planning is a cursor rule published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 2d ago), licensed MIT. It adds 2,170 tokens to every session, about $0.0109 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.