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/pueraeternis/agentic-project-template/02-documentation-workflowgit clone --depth 1 https://github.com/pueraeternis/agentic-project-templateWhat 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.00678 | $0.00678 |
| Opus 5 | $0.00339 | $0.00339 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
02-documentation-workflow 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Workflow
Documentation is the primary engineering artifact.
Implementation follows documented intent.
Permanent project knowledge must be recorded in the repository.
Documentation Responsibilities
Each document has a single responsibility.
| Document | Responsibility |
|---|---|
PROJECT.md |
Project vision, goals, scope and MVP |
ROADMAP.md |
Long-term implementation strategy |
ARCHITECTURE.md |
System organization and architectural boundaries |
ENGINEERING.md |
Engineering decisions, tooling and project conventions |
| ADRs | Significant architectural decisions |
| Plans | Authorized implementation increments |
PROGRESS.md |
Completed engineering history |
RUNBOOK.md |
Operational procedures |
Avoid duplicating information across documents.
Every piece of knowledge should have one authoritative location.
Documentation Lifecycle
Project knowledge matures through the following lifecycle:
Idea
↓
PROJECT.md
↓
ROADMAP.md
↓
ARCHITECTURE.md
↓
ENGINEERING.md
↓
Repository Initialization
↓
Implementation Plan
↓
Implementation
↓
Code Review
↓
PROGRESS.md
Architecture decisions should be recorded as ADRs whenever appropriate.
Documentation Updates
Update documentation whenever:
- project goals change;
- roadmap changes;
- architecture changes;
- engineering decisions change;
- repository structure changes;
- operational procedures change;
- new durable project knowledge appears.
Do not leave important decisions only in chat history.
Engineering Decisions
ENGINEERING.md records project-specific engineering decisions.
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 · 176 lines · 678 tokens per session scan A dbe58c5c06d3
02-documentation-workflow is a cursor rule published in the GitHub repository pueraeternis/agentic-project-template (2 stars, last pushed 2mo ago), licensed MIT. It adds 678 tokens to every session, about $0.0034 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-31.
Other cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.