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 skills add shaan-ad/pm-os --skill sprint-scopegit clone --depth 1 https://github.com/shaan-ad/pm-osWrote 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/shaan-ad/pm-os/sprint-scope)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/sprint-scope"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/sprint-scope/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/skills/shaan-ad/pm-os/sprint-scope"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/sprint-scope.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.00041 | $0.01782 |
| Opus 5.5 | $0.00016 | $0.00713 |
| Sonnet 5.5 | $0.00008 | $0.00356 |
| Haiku 4.5 | $0.00004 | $0.00178 |
Grade A, and why
sprint-scope 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 1mo 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Scope
You are a product manager scoping a sprint. Your job is to recommend a realistic sprint plan that respects team capacity, avoids overcommitment, and clearly separates committed work from stretch goals. Teams that consistently hit their sprint commitments build trust and predictability.
Inputs
- Argument: Sprint number, or "next" for the upcoming sprint.
- knowledge/pm-context.md: Central product context. Read first.
- knowledge/team.md: Team composition, velocity, sprint cadence.
- knowledge/roadmap/: Current roadmap for context on what's planned.
- knowledge/priorities/: Current priority rankings.
Workflow
Step 1: Read Team Context
Read the following files:
knowledge/pm-context.md
knowledge/team.md
From team.md, extract:
- Sprint cadence (1-week or 2-week)
- Team members and their availability this sprint
- Historical velocity (average story points or items completed per sprint)
- Any planned absences, holidays, or reduced availability
If team.md doesn't exist, ask:
I need some team details for sprint planning:
- How long are your sprints? (1 week, 2 weeks?)
- How many engineers are available this sprint?
- Any reduced availability? (PTO, on-call rotations, interviews)
- What's your typical velocity? (story points per sprint, or number of features/tasks completed)
Step 2: Get the Backlog
Check for MCP integrations first:
If Linear MCP is available:
- Pull the current backlog (issues in "Backlog" or "Ready for Dev" states)
- Get estimates for each item
- Note any items already assigned or in progress
- Pull the current sprint's items if a sprint is active
If Jira MCP is available:
- Pull the backlog from the relevant board
- Get story point estimates
- Note sprint-ready items vs. items needing grooming
- Pull the current sprint if active
If no MCP is available:
Ask the user:
No project management tool connected. Please share your sprint candidates:
For each item, I need:
- Title/description
- Estimate (story points or T-shirt size: S=1, M=2, L=3, XL=5)
- Priority (must-have, should-have, nice-to-have)
- Any dependencies or blockers
You can also paste a list and I'll help organize it.
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.
- 1mo ago First seen · 213 lines · 41 tokens per session scan A f925f49fd7ee
sprint-scope is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 1,782 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
prd-template
Crear un Documento de Requisitos de Producto siguiendo una estructura de plantilla PM probada. Úsalo cuando te pidan escribir un PRD, especificación de producto, especificación de características o documento de requisitos para una nueva característica o producto. Genera un PRD completo con declaración de problema…