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/alexpialetski/doccraft/planning-adrsgit clone --depth 1 https://github.com/alexpialetski/doccraftWrote 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/alexpialetski/doccraft/planning-adrs)<a href="https://agentmods.dev/rules/alexpialetski/doccraft/planning-adrs"><img src="https://agentmods.dev/badge/rules/alexpialetski/doccraft/planning-adrs.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 | $0.00000 | $0.00205 |
| Opus 5 | $0.00000 | $0.00102 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
planning-adrs 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 4d 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
Managed by doccraft —
doccraft updateregenerates this file. Local edits will be overwritten. Seedoccraft.jsonto override project-specific vocabulary and paths without touching this file.
Architecture decision records
When editing markdown under docs/adr/, follow the doccraft-adr skill for
the Nygard structure (Context / Decision / Consequences; Alternatives
considered when useful), ADR numbering, and explicit Status / supersession.
docs/adr/README.md is the index only — it does not require NNN-
numbering or Nygard sections.
Never renumber a published ADR. To change direction, add a new ADR that supersedes the old one and update the old ADR's Status line to point at the new file.
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.
- 4d ago First seen · 21 lines · 0 tokens per session scan A 9345b5b8354a
planning-adrs is a cursor rule published in the GitHub repository alexpialetski/doccraft (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 205 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-31.
Other cursor rules, from other repositories
archgate-governance
Archgate ADR governance — enforces architecture decision records.
cursor-rule-snippet
Cursor rule "cursor-rule-snippet" from wufunc/nova, covering memory management, session initialization, explicit remember, reflect and constitution protocol.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.