Borrowing it
Nothing to install: this file belongs to 2233admin/design-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2233admin/design-pipeline/main/.agents/skills/bmad-sprint-planning/SKILL.mdgit clone --depth 1 https://github.com/2233admin/design-pipelineWrote 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/2233admin/design-pipeline/bmad-sprint-planning)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-sprint-planning"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-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/2233admin/design-pipeline/bmad-sprint-planning"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-sprint-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01197 |
| Opus 5 | $0.00034 | $0.00598 |
| Sonnet 5 | $0.00013 | $0.00239 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
bmad-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bmad-sprint-planning — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
You are a senior developer about to commit to this plan. Two moves, in order: first scrutinize the planning the way a skeptic reads a handoff — gaps found now are cheap, gaps found mid-build are not. Then hand the mechanical work to the script: parsing epics, deriving keys, merging statuses, and writing sprint-status.yaml are deterministic jobs, not judgment calls. Your judgment goes where the script can't: deciding which files are epics, weighing readiness, and reconciling anything the script flags.
On Activation
- Resolve customization:
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, read{skill-root}/customize.tomldirectly and use defaults. - Execute each entry in
{workflow.activation_steps_prepend}in order. - Treat every entry in
{workflow.persistent_facts}as foundational context for the rest of the run. Entries prefixedfile:are paths or globs under{project-root}— load the referenced contents as facts. All other entries are facts verbatim. - Load
{project-root}/_bmad/bmm/config.yaml(andconfig.user.yamlif present). Resolve{user_name},{communication_language},{document_output_language},{project_name},{planning_artifacts},{implementation_artifacts},{project_knowledge}(skip gracefully if unset),{date}. Stay in{communication_language}for every turn, not just the greeting. - Greet
{user_name}, detect intent, and load only what that intent needs:- readiness — check implementation readiness only: load
references/readiness-gate.md, run the gate, report, stop - sprint-planning — the full flow (also the refresh path for an existing
sprint-status.yaml): loadreferences/readiness-gate.md, then on PASSreferences/generate-tracking.md - status — "show sprint status", "where are we": skip the gate, load
references/status-view.md - validate — check the tracking file's format: load
references/validate.md - fix — repair or rebuild a broken
sprint-status.yaml: loadreferences/fix-sprint-status.md
- readiness — check implementation readiness only: load
What ships with it
9 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.
- customize.toml 1.6 KB
- references/fix-sprint-status.md 2.7 KB
- references/generate-tracking.md 2.6 KB
- references/readiness-gate.md 1.8 KB
- references/status-view.md 1.6 KB
- references/validate.md 592 B
- scripts/sprint_plan.py 28 KB runs code
- scripts/tests/test_sprint_plan.py 21 KB runs code
- sprint-status-template.yaml 2.3 KB
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 · 63 lines · 67 tokens per session scan A 6ed5dd51be5d
bmad-sprint-planning is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 9d ago), licensed MIT. It adds 67 tokens to every session and 1,197 once invoked, about $0.0003 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
contribution-workflow
Create or document a contribution workflow for a design system — the multi-stage process for evaluating, accepting, and shepherding new contributions through to publication. Trigger when someone says: how should someone contribute, contribution process, adding a new component, contribution guidelines, what's the…
backlog-generator
Transform audit findings into sprint-ready work items with effort estimates, acceptance criteria, and stakeholder-friendly rationale. This converts existing findings into tickets, NOT the process for contributing new components to the system. Trigger when someone says: generate backlog items, create tickets from…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
ss-reference
Compile screenshots, URLs, Figma exports, or an existing UI into a project-local StyleSeed output grammar with evidence, tokens, confidence, anti-patterns, and a validation screen. Use when the user supplies a design reference that StyleSeed does not already model.