phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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 commands/phuryn/pm-skills/sprintgit clone --depth 1 https://github.com/phuryn/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/phuryn/pm-skills/sprint)<a href="https://agentmods.dev/commands/phuryn/pm-skills/sprint"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/sprint.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.00015 | $0.01205 |
| Opus 5 | $0.00008 | $0.00602 |
| Sonnet 5 | $0.00003 | $0.00241 |
| Haiku 4.5 | $0.00002 | $0.00120 |
Grade A, and why
sprint 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sprint — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sprint -- Sprint Lifecycle
Three modes covering the sprint lifecycle: plan for sprint planning, retro for retrospectives, release-notes for shipping communication.
Invocation
/sprint plan 2-week sprint, 4 engineers, focus on checkout improvements
/sprint retro [paste team feedback or sprint data]
/sprint release-notes [paste tickets, changelog, or PRD]
/sprint # asks which phase you're in
Modes
Plan Mode
Prepare for sprint planning with capacity estimation, story selection, and risk identification.
Workflow
Step 1: Gather Sprint Context
- Sprint duration (1 or 2 weeks)
- Team composition (engineers, designers, QA — and availability)
- Sprint goal or focus area
- Backlog items to consider (paste, upload, or describe)
- Any carry-over from last sprint
- Known interruptions (holidays, on-call, meetings)
Step 2: Estimate Capacity
Apply the sprint-plan skill:
- Calculate available engineering hours/points after meetings, on-call, PTO
- Apply a velocity adjustment based on historical data (if provided) or industry standard (70% of theoretical capacity)
- Show capacity breakdown per team member
Step 3: Select and Sequence Stories
- Recommend which stories fit within capacity
- Flag dependency chains (A must complete before B starts)
- Identify risks: stories that are underspecified, have external dependencies, or need design input
- Balance quick wins with larger items
- Ensure every story has acceptance criteria
Step 4: Generate Sprint Plan
## Sprint Plan: [Sprint Name/Number]
**Duration**: [dates]
**Sprint Goal**: [one sentence]
**Team**: [members and availability]
### Capacity
| Member | Available Days | Points/Hours | Notes |
|--------|--------------|-------------|-------|
**Total capacity**: [X] points/hours
**Recommended commitment**: [Y] points/hours (with buffer)
### Selected Stories
| # | Story | Points | Owner | Dependencies | Risk |
|---|-------|--------|-------|-------------|------|
### Sprint Risks
1. [Risk] — Mitigation: [action]
### Definition of Done
- [ ] Code reviewed
- [ ] Tests passing
- [ ] Deployed to staging
- [ ] QA approved
- [ ] Documentation updated (if applicable)
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.
- 7d ago First seen · 194 lines · 15 tokens per session scan A 411d61287f69
sprint is a command published in the GitHub repository phuryn/pm-skills (26,033 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 1,205 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
version-bump
Bump versions across the monorepo during release process.
frankx-ai-deploy
Deploy FrankX.AI website changes to Vercel with quality checks.
plan-sync
Sync all plan-related files to the production worktree and deploy.
buyer-personas
Map the buying committee, then build alternatives-anchored messaging personas.
ideal-customer-profile
Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.
experiment-ideas
Generate several concrete, brain-grounded growth ideas — channel, message, rationale, cost-efficiency — ranked by effort vs. impact.