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 skills/aakashg/pm-claude-code-setup/sprint-plannernpx skills add aakashg/pm-claude-code-setup --skill sprint-plannergit clone --depth 1 https://github.com/aakashg/pm-claude-code-setupWrote 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/skills/aakashg/pm-claude-code-setup/sprint-planner)<a href="https://agentmods.dev/skills/aakashg/pm-claude-code-setup/sprint-planner"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-code-setup/sprint-planner.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.00000 | $0.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
sprint-planner 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 6d 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
Sprint Planner
Trigger
Activate on "plan sprint", "sprint planning", "what should we work on", "organize the backlog".
Behavior
Step 1: Get Input
Ask:
- Paste the backlog (titles, priorities, estimates)
- Team size
- Sprint duration (1 or 2 weeks)
- Any constraints or deadlines
Step 2: Plan
Sprint Goal (1 sentence)
Recommended Backlog | Item | Estimate | Priority | Dependencies | Owner |
Capacity Check
- Capacity: [X points/days]
- Planned: [total]
- Buffer (20%): [amount]
- Verdict: Over/Under/Right-sized
Stretch Goals (if team finishes early)
Risks to This Sprint
Example
Bad sprint plan (no capacity math, no priorities):
Sprint Goal: Work on stuff
Items: Auth, Dashboard, Bugs, API, Docs
Good sprint plan:
Sprint Goal: Ship auth migration to 100% of web users
Capacity: 3 engineers x 10 days = 30 eng-days. At 80% = 24 available.
| Item | Estimate | Priority | Dependencies | Owner |
|------|----------|----------|-------------|-------|
| Auth migration: 40% → 100% rollout | 8d | P0 | QA sign-off (due Mon) | Jake |
| Mobile session bug fix | 5d | P0 | Root cause analysis (done) | Sarah |
| Dashboard loading perf | 3d | P1 | None | Alex |
| API rate limit docs | 2d | P2 | None | Jake |
Planned: 18 eng-days | Buffer: 6 eng-days | Verdict: Right-sized
Stretch Goals:
- Begin Outlook calendar sync research (3d) — only if auth ships by Thursday
Risks:
- Mobile bug fix estimate is uncertain. If root cause is deeper than
diagnosed, it could take 8d instead of 5d. Mitigation: Jake pairs
with platform team. If not resolved by Wednesday, descope and carry
to next sprint.
Rules
- 80% capacity is the ceiling. Sprints loaded above 80% have a >50% chance of missing the goal.
- Flag items with unclear requirements. Unclear requirements are estimation landmines.
- Unresolved dependencies block sprint entry. Resolve before committing the item.
- Every item needs a definition of done.
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.
- 6d ago First seen · 70 lines · 0 tokens per session scan A fa479ce33258
sprint-planner is a skill published in the GitHub repository aakashg/pm-claude-code-setup (152 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 tokens. 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 skills, from other repositories
create-slide-deck
Create beautiful HTML slide decks for product presentations. Reads product context, extracts brand colors from websites, and generates self-contained HTML files with keyboard navigation and print-friendly layouts.
pm-setup
Interactive onboarding wizard that creates the PM-OS knowledge base for your product. Asks questions, fetches company info, and populates all knowledge files.
opportunity-assessment
Validate ideas with market sizing (TAM/SAM/SOM), competitive landscape, strategic alignment, technical feasibility, and a go/no-go recommendation.
competitive-intel
Research a competitor from their URL or name. Fetch website, pricing, features, and news. Generate a battlecard with positioning, strengths, weaknesses, and strategic implications.
experiment-review
Analyze A/B tests and experiments with statistical rigor, assess significance, perform segment analysis, and produce a clear ship/kill/extend recommendation.
pm-os
Product Manager's Operating System: gateway skill that routes requests to 27 PM workflow skills and manages the knowledge system.