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 abrahamFerga/scrum-skills --skill sprint-planninggit clone --depth 1 https://github.com/abrahamFerga/scrum-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/skills/abrahamferga/scrum-skills/sprint-planning)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/sprint-planning"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/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/skills/abrahamferga/scrum-skills/sprint-planning"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/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.00113 | $0.01255 |
| Opus 5 | $0.00056 | $0.00628 |
| Sonnet 5 | $0.00023 | $0.00251 |
| Haiku 4.5 | $0.00011 | $0.00126 |
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 12d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planning
Scrum Guide grounding
Sprint Planning kicks off the Sprint. The whole Scrum Team attends — Developers, the Product Owner, and the Scrum Master. It is time-boxed to eight hours for a one-month Sprint (shorter for shorter Sprints).
The event answers three questions:
| Topic | Question |
|---|---|
| Why | What is the Sprint Goal — the single objective that makes this Sprint worthwhile? |
| What | Which Product Backlog items can the Developers commit to completing? |
| How | How will the selected work get done? |
The Sprint Goal is the output that matters most. It gives the team coherence and the flexibility to negotiate scope during the Sprint.
Tool detection
Identify which project management tool is available before proceeding:
- Check for active
mcp__azure-devops__*tools → set$PM_TOOLtoado - Otherwise check for active
mcp__jira__*tools → set$PM_TOOLtojira - If both → ask: "I see both ADO and Jira connected — which should I use?"
- If neither → set
$PM_TOOLtomanual
Step 1 — Establish context
Ask for any missing context before pulling data:
- "What is the Sprint length?" (default: 2 weeks)
- "What is the team's capacity this Sprint?" (total developer-days, accounting for time off)
- "Is there a Product Goal or theme the Sprint should contribute to?"
Store as $SPRINT_LENGTH, $CAPACITY, $PRODUCT_GOAL.
Step 2 — Fetch the top of the Product Backlog
Retrieve the ordered, refined items at the top of the backlog:
- ADO: use
wit_list_backlog_work_itemsorwit_list_backlogsfor the current project - Jira: use the equivalent backlog listing tool, ordered by rank
- Manual: ask the Product Owner to paste or describe the top 10–15 items
Present the items as a numbered list with ID, title, and current state. Flag any item that appears unrefined (no acceptance criteria, no size estimate) with a ⚠️.
Step 3 — Craft the Sprint Goal
A good Sprint Goal is:
- A single, coherent objective — not a list of features
- Outcome-oriented, not a task list
- Achievable within the Sprint
- Meaningful to stakeholders
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.
- 12d ago First seen · 134 lines · 113 tokens per session scan A 5829bf50e53c
sprint-planning is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 113 tokens to every session and 1,255 once invoked, about $0.0006 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-31.
Other skills, from other repositories
turborepo
Skill "turborepo" from ashish7802/awesome-api-skills, covering turborepo skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
devflow-planning
AI-powered sprint planning, velocity analysis, and capacity forecasting. Use for planning sprints, predicting outcomes, and providing agile recommendations based on historical data.
git-jira-integration
Integration between Git workflows and Jira issues. Generates branch names from issues, validates commit messages, and provides PR context from Jira specifications.