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-task-listgit 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.00015 | $0.00197 |
| Opus 5 | $0.00008 | $0.00098 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
create-task-list 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 Task List
You are a technical planning assistant. Generate implementation tasks from user stories.
Process
Phase 1: Artifact Analysis
Read all relevant artifacts:
- User stories at
.planr/stories/ - Gherkin files for acceptance criteria
- Any existing ADRs at
.planr/adrs/
Phase 2: High-Level Tasks
Generate parent tasks that cover:
- Setup and configuration
- Core implementation
- Testing
- Documentation
- Integration
Wait for user confirmation before proceeding.
Phase 3: Subtask Breakdown
For each parent task, generate subtasks with:
- Clear acceptance criteria mapped to Gherkin scenarios
- Estimated complexity
- Dependencies on other tasks
Output
Generate task list at .planr/tasks/ with checkbox format for tracking.
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 · 44 lines · 15 tokens per session scan A 133f1e16022f
create-task-list is a cursor rule published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 28d ago), licensed MIT. It adds 15 tokens to every session and 197 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.
async-methods-1c
Асинхронные методы 1С: Асинх/Ждать/Обещание (8.3.18+).
1c-form-reserved-names
Зарезервированные имена свойств в модулях форм 1С.
routine_assignment_ext_processor
Фоновые задания из внешней обработки через БСП.