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 agentmods add skills/re-cinq/wave/bmadnpx skills add re-cinq/wave --skill bmadgit clone --depth 1 https://github.com/re-cinq/waveWhat 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 | $0.00035 | $0.00867 |
| Opus 5 | $0.00017 | $0.00434 |
| Sonnet 5 | $0.00007 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
bmad 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMAD - Breakthrough Method for Agile AI-Driven Development
BMAD provides a comprehensive methodology for AI-enhanced development workflows with role-based agent specialization and structured collaborative development processes.
Overview
BMAD implements two distinct development paths:
Quick Path (Bug fixes & small features)
Streamlined workflow for small work items (< 1 week):
- Quick Specification - Analyze codebase and create tech spec with stories
- Development - Implement individual stories
- Code Review - Validate quality and compliance
Full Path (Products & complex features)
Comprehensive planning workflow for major initiatives (> 1 week):
- Product Brief → PRD → Architecture → Epic Breakdown → Sprint Planning → Story Development → Code Review
Available Commands
Quick Path
| Command | Purpose | Usage |
|---|---|---|
bmad.quick-spec |
Analyze codebase and create tech spec with stories | /bmad.quick-spec "description" |
bmad.dev-story |
Implement a single story from spec | /bmad.dev-story [story-id] |
bmad.gh-pr-review |
Validate code quality and compliance | /bmad.gh-pr-review |
Full Path
| Command | Purpose | Usage |
|---|---|---|
bmad.product-brief |
Define problem, users, and MVP scope | /bmad.product-brief "product name" |
bmad.prd |
Create detailed Product Requirements Document | /bmad.prd |
bmad.architecture |
Create technical architecture document | /bmad.architecture |
bmad.epics |
Create prioritized epic and story breakdown | /bmad.epics |
bmad.sprint |
Initialize sprint tracking | /bmad.sprint |
bmad.story |
Create detailed story specification | /bmad.story [epic-id] |
Utility
| Command | Purpose | Usage |
|---|---|---|
bmad.help |
Get contextual guidance and command suggestions | /bmad.help [question] |
bmad.party |
Multi-agent collaborative session | /bmad.party [topic] |
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.
- 2d ago First seen · 89 lines · 35 tokens per session scan A 5cf2d7c4dcdc
bmad is a skill published in the GitHub repository re-cinq/wave (20 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 867 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-08-30.
Other skills, from other repositories
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
flow-next-pilot
Single-tick autonomous build-loop conductor. Advances one ready spec one stage per tick, emits PILOTVERDICT. Use when asked to pilot a spec or backlog.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
sprint-planning
Plan implementation sprints with story selection, goal definition, and execution ordering.
kanban-management
Initialize and manage Kanban board state for feature workflow tracking.
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.