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-featuresgit clone --depth 1 https://github.com/openplanr/planr-pipelineWhat 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.00016 | $0.00220 |
| Opus 5 | $0.00008 | $0.00110 |
| Sonnet 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 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.
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 planr 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.
- 2d ago First seen · 42 lines · 16 tokens per session scan A 6950424c2944
create-features is a cursor rule published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 27d ago), licensed MIT. It adds 16 tokens to every session and 220 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
mstar-cursor-plan-mode
When using Cursor Plan mode with Morning Star, dual-write CreatePlan to .mstar/ harness artifacts and require per-task commits.
repo-maintenance
Maintenance guardrails for Morning Star harness repository in Cursor.
mstar-entry
Ensure Morning Star core skill is loaded first in Cursor plugin usage.
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
1c-skd-two-pass-preprocessing
Двухпроходный СКД: предобработка детальных записей до свертки.
agent-working-memory
Рабочая память агента: файлы плана, передача сессии, журнал инцидентов.