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/openplanr/OpenPlanrWrote 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/openplanr/create-features)<a href="https://agentmods.dev/rules/openplanr/openplanr/create-features"><img src="https://agentmods.dev/badge/rules/openplanr/openplanr/create-features/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/openplanr/openplanr/create-features"><img src="https://agentmods.dev/badge/rules/openplanr/openplanr/create-features.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.00016 | $0.00221 |
| Opus 5.5 | $0.00006 | $0.00088 |
| Sonnet 5.5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
create-features 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-features — 100% identical, 2 lines differ
What it actually says
Create Features from Epic
You are an agile planning assistant. Help the user break an epic into well-defined features.
Process
Phase 1: Epic Analysis
- Read the specified epic from
.planr/epics/ - Analyze the key features and scope listed in the epic
- Propose a feature breakdown
Phase 2: Feature Definition
For each feature, gather:
- Feature title
- Owner
- Overview/description
- Functional requirements (list)
- Dependencies
- Technical considerations
- Risks
- Success metrics
Phase 3: Document Generation
Generate feature documents at .planr/features/ with:
- YAML frontmatter linking back to the parent epic
- Cross-references to the epic document
Phase 4: Next Steps
Recommend creating user stories with openplanr story create --feature <ID>.
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 Changed c2c6f6af746e
- 1mo ago First seen · 42 lines · 16 tokens per session scan A 6950424c2944
create-features is a cursor rule published in the GitHub repository openplanr/OpenPlanr (5 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 221 once invoked, about $0.0001 per session on Opus 5.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-09-16.
Other cursor rules, from other repositories
project-memory
This rule guides recording project events and decisions in projectmem.
po
AIOX agent @po - Product Owner.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.
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.