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 The-AI-Directory-Company/agents-and-skills --skill sprint-planning-guidegit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/sprint-planning-guide)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/sprint-planning-guide"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/sprint-planning-guide/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/the-ai-directory-company/agents-and-skills/sprint-planning-guide"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/sprint-planning-guide.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.00030 | $0.01522 |
| Opus 5 | $0.00015 | $0.00761 |
| Sonnet 5 | $0.00006 | $0.00304 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
sprint-planning-guide 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planning Guide
Before you start
Gather the following from the user:
- Sprint length (1 week, 2 weeks, or custom)
- Team size and composition (How many engineers, designers, QA — and who is out this sprint)
- Backlog state (Is the backlog refined? Are the top items estimated and acceptance-criteria-ready?)
- Carryover from last sprint (Incomplete stories, bugs, or tech debt items that must continue)
- External commitments (Deadlines, cross-team dependencies, or stakeholder promises)
If the user says "we just pull from the top of the backlog," push back: "Without a sprint goal, the team is doing task execution, not sprint planning. What outcome should be true at the end of this sprint that isn't true today?"
Sprint planning template
1. Pre-Planning: Backlog Refinement
Complete this before the planning meeting — not during it.
Refinement checklist (done 2-3 days before planning):
- Top 15-20 backlog items have clear descriptions and acceptance criteria
- Stories are estimated (story points, T-shirt sizes, or hours — pick one, stay consistent)
- Dependencies between stories are identified and documented
- Stories that require design, research, or external input are flagged
- Tech debt and bug items are groomed and prioritized alongside feature work
If the backlog isn't refined, don't hold planning. Hold a refinement session instead. Planning with unrefined stories wastes everyone's time and produces unreliable commitments.
2. Capacity Calculation
Calculate how much the team can realistically take on.
Team capacity worksheet:
| Team Member | Available Days | Focus Factor | Effective Days |
|-------------|---------------|-------------|----------------|
| Alice | 10 | 0.8 | 8.0 |
| Bob | 8 (PTO Fri) | 0.8 | 6.4 |
| Carol | 10 | 0.7 (on-call)| 7.0 |
| Dave | 5 (half sprint)| 0.8 | 4.0 |
| **Total** | **33** | | **25.4** |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 127 lines · 30 tokens per session scan A 226039d9a5df
sprint-planning-guide is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 1,522 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
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.