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/product-on-purpose/pm-skillsWrote 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/commands/product-on-purpose/pm-skills/workflow-sprint-planning)<a href="https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-sprint-planning"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-sprint-planning/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/commands/product-on-purpose/pm-skills/workflow-sprint-planning"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-sprint-planning.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.00014 | $0.00252 |
| Opus 5 | $0.00007 | $0.00126 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
workflow-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 11d 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
Run the Sprint Planning workflow to prepare sprint-ready stories from a backlog or PRD.
This workflow uses multiple skills in sequence. For each step, read the skill instructions and follow them to create the artifact.
Workflow Steps
Step 1: Refinement Notes
Use the iterate-refinement-notes skill from skills/iterate-refinement-notes/SKILL.md.
Document the backlog refinement session: stories discussed, estimates, questions raised, and decisions made.
Step 2: User Stories
Use the deliver-user-stories skill from skills/deliver-user-stories/SKILL.md.
Generate user stories with clear acceptance criteria from the refined backlog items.
Step 3: Edge Cases
Use the deliver-edge-cases skill from skills/deliver-edge-cases/SKILL.md.
Document edge cases, error states, and boundary conditions for the stories from Step 2.
Output
Create all three artifacts in sequence, ensuring each builds on the previous.
Reference the Sprint Planning workflow at _workflows/sprint-planning.md for additional guidance.
Context from user: $ARGUMENTS
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.
- 11d ago First seen · 36 lines · 14 tokens per session scan A 7d865b53eab9
workflow-sprint-planning is a command published in the GitHub repository product-on-purpose/pm-skills (658 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 252 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-30.
Other commands, from other repositories
discover
Structured product discovery from problem to validated experiments.
okr-planning
Structured OKR creation aligned with company objectives.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
epic-dev
Epic/sprint development workflow with git worktrees, GitHub issues, and phased delivery.
triage
Triages an unprioritized list of bugs, debt, and tasks into a full MoSCoW breakdown with justification and an attack order.