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 mannnrachman/pi-bmad --skill bmad-sprint-planninggit clone --depth 1 https://github.com/mannnrachman/pi-bmadWrote 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/mannnrachman/pi-bmad/bmad-sprint-planning)<a href="https://agentmods.dev/skills/mannnrachman/pi-bmad/bmad-sprint-planning"><img src="https://agentmods.dev/badge/skills/mannnrachman/pi-bmad/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/mannnrachman/pi-bmad/bmad-sprint-planning"><img src="https://agentmods.dev/badge/skills/mannnrachman/pi-bmad/bmad-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.00076 | $0.01212 |
| Opus 5 | $0.00038 | $0.00606 |
| Sonnet 5 | $0.00015 | $0.00242 |
| Haiku 4.5 | $0.00008 | $0.00121 |
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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.5 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.
- 2d ago Changed · +9 tokens per session 7365485e19e2
- 11d ago First seen · 63 lines · 67 tokens per session scan A 533d704672eb
bmad-sprint-planning is a skill published in the GitHub repository mannnrachman/pi-bmad (2 stars, last pushed 3d ago), with no licence file. It adds 76 tokens to every session and 1,212 once invoked, about $0.0004 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
bmad-epics-and-stories
Solutioning flagship — shards a PRD + architecture into epics.md and individual {epic}.{story}.{slug}.story.md context objects, the LAST planning artifact before external dev handoff. Each story is a self-contained 8K-token compiled context object: Dev Notes with SOURCE CITATIONS back to prd.md/architecture.md…
bmad-parallel-plan
Turns a sequential, ready-for-dev story backlog into conflict-free CONCURRENT WAVES. Builds a dependency DAG from epic order, per-story dependency maps, and Owned File/Module Scope overlaps, then topologically sorts it into parallel waves of mutually disjoint, dependency-satisfied stories (capped by maxParallel), and…
bmad-sprint-planning
Orchestration handoff bridge: emits and maintains sprint-status.yaml as the project's sequencing system-of-record. Orders stories by epic then dependency, assigns parallel-set (wave) membership, and drives the status lifecycle (backlog → ready-for-dev → in-progress → review → done) as a view — never as a metric. Use…
bmad-epic-pipeline-worktree
Deliver entire Epic using configurable pipeline in isolated worktrees.
bmad-story-pipeline
Run configurable BMAD pipeline for story delivery using subagent.
bmad-correct-course
CROSS-PHASE mid-stream scope correction. Re-enters planning when requirements, features, architecture, or constraints change after planning has started. Re-shards affected epics/stories, re-sequences sprint-status.yaml, appends rationale to decision-log.md. Routes to bmad-epics-and-stories, bmad-sprint-planning, or…