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 w95/awesome-claude-corporate-skills --skill sprint-planninggit clone --depth 1 https://github.com/w95/awesome-claude-corporate-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/w95/awesome-claude-corporate-skills/sprint-planning)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/sprint-planning"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-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/w95/awesome-claude-corporate-skills/sprint-planning"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-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.00040 | $0.03957 |
| Opus 5 | $0.00020 | $0.01978 |
| Sonnet 5 | $0.00008 | $0.00791 |
| Haiku 4.5 | $0.00004 | $0.00396 |
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 9d 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 — 534 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planning
Overview
The Sprint Planning skill enables product managers and engineering leaders to organize work into effective sprints that balance delivery with quality. It covers goal-setting, capacity planning, story estimation, and retrospective analysis for continuous improvement.
When to Use This Skill
- Planning 2-week or 1-week sprints
- Estimating feature complexity and effort
- Balancing feature work with technical debt
- Setting realistic sprint commitments
- Conducting effective sprint kickoffs
- Running productive retrospectives
- Improving team velocity and processes
Sprint Planning Framework
Pre-Planning Preparation (1 week before)
Step 1: Backlog Grooming
- Review top 20 backlog items
- Ensure items have clear acceptance criteria
- Clarify any ambiguous requirements with PM
- Break down large items into 2-4 point stories
- Mark dependencies and blockers
- Update priority ordering
Step 2: Capacity Planning
- Count available person-days (total days - planned PTO)
- Account for meetings and overhead (20% typical)
- Calculate net capacity for dev work
- Identify team members with special focus areas
Step 3: Dependency Review
- Identify items blocked by previous sprints
- Ensure unblocking work is prioritized
- Flag external dependencies (design, third-party)
- Plan workarounds for external delays
Story Point Estimation
Estimation Framework (Fibonacci Scale)
Story points represent relative complexity/effort, not hours
1 point - Trivial changes: typo fixes, simple config updates
Example: "Fix button color from blue to red"
2 points - Simple changes: straightforward feature, 1-2 day effort
Example: "Add email field to user profile form"
3 points - Small feature: touches 1-2 components, clear requirements
Example: "Implement forgot password email flow"
5 points - Medium feature: crosses multiple systems, some complexity
Example: "Add two-factor authentication"
8 points - Complex feature: significant complexity, multiple dependencies
Example: "Build real-time notification system"
13 points - Very complex: major feature, high uncertainty
Example: "Rebuild authentication system"
21 points - Epic (break down): too large for single sprint
Example: "Complete mobile app redesign"
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.
- 9d ago First seen · 534 lines · 40 tokens per session scan A 71472b2ea1c8
sprint-planning is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 3,957 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.