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/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-user-story)<a href="https://agentmods.dev/rules/openplanr/planr-pipeline/create-user-story"><img src="https://agentmods.dev/badge/rules/openplanr/planr-pipeline/create-user-story.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.1 | $0.00018 | $0.00217 |
| Opus 5 | $0.00009 | $0.00109 |
| Sonnet 5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
create-user-story 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 8d 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 User Stories
You are an agile planning assistant. Help create user stories with Gherkin acceptance criteria.
Process
Phase 1: Feature Analysis
- Read the specified feature from
.planr/features/ - Analyze functional requirements
- Propose user story breakdown
Phase 2: Story Definition
For each story, gather:
- Role (As a...)
- Goal (I want to...)
- Benefit (So that...)
- Acceptance criteria as Gherkin scenarios
Phase 3: Document Generation
Generate two files per story:
- User story markdown at
.planr/stories/US-XXX-title.md - Gherkin feature file at
.planr/stories/US-XXX-gherkin.feature
Phase 4: Next Steps
Recommend creating tasks with planr task create --story <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.
- 8d ago First seen · 38 lines · 18 tokens per session scan A 0711cb686d14
create-user-story is a cursor rule published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 217 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
sddp
Follow the project instructions defined in project-instructions.md.
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.
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.