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/rm2thaddeus/pixel_detective/sprint-planninggit clone --depth 1 https://github.com/rm2thaddeus/Pixel_DetectiveWrote 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/rm2thaddeus/pixel_detective/sprint-planning)<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/sprint-planning"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/sprint-planning.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.00005 | $0.01942 |
| Opus 5 | $0.00003 | $0.00971 |
| Sonnet 5 | $0.00001 | $0.00388 |
| Haiku 4.5 | $0.00001 | $0.00194 |
Grade A, and why
sprint-planning 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Updated Sprint Planning Rules - Post Reorganization
Purpose: Comprehensive sprint planning workflow using organized documentation structure and MCP server integration.
📋 New Sprint Documentation Structure
Based on the reorganization completed, all sprint planning should follow this logical structure:
Organized Documentation Hierarchy
docs/sprints/
├── sprint-{number}/ # Sprint-specific deliverables
│ ├── README.md # Sprint overview and status
│ ├── PRD.md # Product Requirements Document
│ ├── technical-implementation-plan.md # Technical details
│ ├── completion-summary.md # Post-sprint results
│ ├── QUICK_REFERENCE.md # Fast lookup guide
│ ├── PERFORMANCE_BREAKTHROUGH.md # Major technical achievements
│ └── transition-to-next-sprint.md # Handoff planning
├── planning/ # Cross-sprint coordination
│ ├── SPRINT_STATUS.md # Multi-sprint tracking
│ ├── sprint-coordination.md # Transition protocols
│ └── sprint-transition-notes.md # Planning coordination
└── templates/ # Reusable templates
├── create-sprint.md # Sprint setup guide
└── PRD-template.md # PRD template
Project-Level vs Sprint-Level Documents
✅ Keep in main /docs/ (Project-Wide):
PROJECT_STATUS.md- Overall project health dashboardREADME.md- Project overviewroadmap.md- Long-term development planningarchitecture.md- Technical architectureCLI_ENTERPRISE_VISION.md- Enterprise strategy
✅ Move to /docs/sprints/ (Sprint-Specific):
- All sprint deliverables and documentation
- Performance breakthrough reports
- Sprint transition planning
- Cross-sprint coordination tracking
🚀 Updated Sprint Planning Workflow
Phase 1: Sprint Setup (Updated Directory Creation)
1.1 Create Sprint Structure
# Create new sprint directory
mkdir -p docs/sprints/sprint-{number}
# Initialize with templates
cp docs/sprints/templates/PRD-template.md docs/sprints/sprint-{number}/PRD.md
# Create initial README from template
# (Use Sprint 02 README.md as reference)
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 · 234 lines · 5 tokens per session scan A fc2d6729ea2a
sprint-planning is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 1,942 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
development-workflow
AAMAD modular development workflow for context-aware agent coordination.
checkpoint
Write a committed handoff checkpoint so a fresh session can resume with zero loss. Use when crossing the 40% context line, on every stage transition, and at session end. Writes .trace/checkpoints/ - .md while the agent is still sharp.
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.