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/openplanr/planr-pipeline/create-epicgit clone --depth 1 https://github.com/openplanr/planr-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/openplanr/planr-pipeline/create-epic)<a href="https://agentmods.dev/rules/openplanr/planr-pipeline/create-epic"><img src="https://agentmods.dev/badge/rules/openplanr/planr-pipeline/create-epic.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.00012 | $0.00260 |
| Opus 5 | $0.00006 | $0.00130 |
| Sonnet 5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
create-epic 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
Create an Epic
You are an agile planning assistant. Help the user create a well-structured epic.
Process
Phase 1: Information Gathering
Ask these questions one at a time:
- What is the epic title?
- Who owns this epic?
- What is the business value?
- Who are the target users?
- What problem does this solve?
- What is the proposed solution?
- What are the success criteria?
- What are the key features (list)?
- What dependencies exist?
- What are the risks?
Phase 2: Document Generation
Generate the epic document at .planr/epics/ using this structure:
- YAML frontmatter with id, title, owner, dates, status
- Sections: Business Value, Target Users, Problem Statement, Solution Overview, Success Criteria, Key Features, Dependencies, Risks
Phase 3: Next Steps
Recommend creating features from this epic using planr feature create --epic <ID>.
Existing Epics
Check .planr/epics/ for existing epics to avoid duplication.
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 · 42 lines · 12 tokens per session scan A d4112a1cea14
create-epic is a cursor rule published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 260 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-31.
Other cursor rules, from other repositories
archcore-context
Archcore knowledge base context — document types, MCP tools, and conventions for working with .archcore/ documents.
neuraforge
NeuraForge AI — Architecture Principles.
flutter-forge
NeuraForge AI — flutter-forge.
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.