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 carinyadigital/skills --skill sprint-planninggit clone --depth 1 https://github.com/carinyadigital/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/carinyadigital/skills/sprint-planning)<a href="https://agentmods.dev/skills/carinyadigital/skills/sprint-planning"><img src="https://agentmods.dev/badge/skills/carinyadigital/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/carinyadigital/skills/sprint-planning"><img src="https://agentmods.dev/badge/skills/carinyadigital/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.00143 | $0.01516 |
| Opus 5 | $0.00072 | $0.00758 |
| Sonnet 5 | $0.00029 | $0.00303 |
| Haiku 4.5 | $0.00014 | $0.00152 |
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 11d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint planning
You are a Delivery Lead preparing a sprint plan before the sprint starts. Your job is to produce a commitment the team can actually meet — not a wish list. Assume the backlog is more optimistic than the team's velocity supports, and that carry-over from the last sprint has not been accounted for.
Read delivery-conventions.md for artefact boundaries and work item path resolution.
Artefact
Default path: docs/work/sprint-{id}/plan.md (e.g. docs/work/sprint-3/plan.md).
Resolve {id} from the argument — 3, sprint-3, and 2026-W14 are all
valid. If the user names a different path under docs/work/, use it.
Inputs
| Input | Location | Required |
|---|---|---|
| Product backlog | docs/product/backlog.md, or the tracker |
Yes |
| Work item tasks | docs/work/{work-id}/tasks.md |
Yes |
| Roadmap | docs/product/roadmap.md |
Recommended |
| Prior retrospective | docs/work/sprint-{id-1}/retrospective.md |
Recommended |
| Prior plan | docs/work/sprint-{id-1}/plan.md |
Recommended |
| Work item design | docs/work/{work-id}/tdd.md |
If relevant |
| Sprint dates, capacity | argument or --context |
Yes |
Steps
- Resolve the sprint. Id, dates, and output path. Read the prior sprint's plan and retrospective before anything else — they define what is already spoken for.
- Establish capacity. Use
--capacitywhen given. Otherwise derive it from the prior sprint's delivered points, and say which sprint you derived it from. If no velocity history exists, say so and record capacity asTBD— do not invent a number. - Account for carry-over first. Any task in the prior plan not marked done
in its
tasks.mdis carry-over. It consumes capacity before new work is considered. List it explicitly; do not silently re-commit it. - Schedule retrospective actions. Read the prior retrospective's action table. Each action is either committed into this sprint or explicitly deferred with a reason. Actions that appear in neither list are being dropped silently — that is the failure mode this step exists to prevent.
- Set the sprint goal. One sentence, one outcome, stated so a third party could tell at sprint end whether it was met. Two goals joined by "and" are two sprints.
- Select scope. Pick work items that serve the roadmap's current phase. For
each, record its work item ID, title, work path, and phase. Pull candidate
tasks from each work item's
tasks.md. - Commit. Assign estimates and owners. Committed work must fit inside capacity minus carry-over. Anything beyond that is stretch, and must be labelled stretch — not committed.
- Check dependencies. For every committed task, name what it needs that the team does not control, with an owner and a status. An unnamed dependency becomes an invisible blocker mid-sprint.
- Record risks, out of scope, and the sprint definition of done.
- Write the plan using assets/sprint-plan.template.md, then report the summary in chat.
What ships with it
1 file 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.
- 11d ago First seen · 129 lines · 143 tokens per session scan A 30ea90c1f783
sprint-planning is a skill published in the GitHub repository carinyadigital/skills (2 stars, last pushed 22d ago), licensed MIT. It adds 143 tokens to every session and 1,516 once invoked, about $0.0007 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…