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-help/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-help)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-help"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-help.svg" alt="Measured on agentmods" 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.00051 | $0.01008 |
| Opus 5 | $0.00026 | $0.00504 |
| Sonnet 5 | $0.00010 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
bmad-help 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 7d 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.
This is a copy
84% identical to bmad-help — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMad Help
Purpose
Help the user understand where they are in their BMad workflow and what to do next, and also answer broader questions when asked that could be augmented with remote sources such as module documentation sources.
Desired Outcomes
When this skill completes, the user should:
- Know where they are — which module and phase they're in, what's already been completed
- Know what to do next — the next recommended and/or required step, with clear reasoning
- Know how to invoke it — skill name, menu code, action context, and any args that shortcut the conversation
- Get offered a quick start — when a single skill is the clear next step, offer to run it for the user right now rather than just listing it
- Feel oriented, not overwhelmed — surface only what's relevant to their current position; don't dump the entire catalog
- Get answers to general questions — when the question doesn't map to a specific skill, use the module's registered documentation to give a grounded answer
Data Sources
- Catalog:
{project-root}/_bmad/_config/bmad-help.csv— assembled manifest of all installed module skills - Config: Run
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}and use the merged JSON to resolveoutput-locationvariables and readcore.communication_languageandmodules.bmm.project_knowledge. The resolver merges_bmad/config.toml,_bmad/config.user.toml,_bmad/custom/config.toml, and_bmad/custom/config.user.tomlin that order. - Artifacts: Files matching
outputspatterns at resolvedoutput-locationpaths reveal which steps are possibly completed; their content may also provide grounding context for recommendations - Project knowledge: If
project_knowledgeresolves to an existing path, read it for grounding context. Never fabricate project-specific details. - Module docs: Rows with
_metain theskillcolumn carry a URL or path inoutput-locationpointing to the module's documentation (e.g., llms.txt). Fetch and use these to answer general questions about that module.
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.
- 7d ago First seen · 76 lines · 51 tokens per session scan A 68a19089a007
bmad-help is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 1,008 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to bmad-help, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
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-pattern
Generate a composed UI pattern from the active StyleSeed grammar and brand recipe using existing primitives.
ss-restyle
Apply one optional StyleSeed aesthetic profile without changing the selected output grammar, product job, or core design judgment.
governance-encoder
Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…
token-documentation
Write documentation for design tokens — covering semantic intent, usage context, and do/don't examples. Trigger when someone says: document these tokens, token reference, what does this token mean, token usage guide, write the token docs, token intent, or anything about creating human-readable documentation for design…