Borrowing it
Nothing to install: this file belongs to jeffrey2423/commit-like-pro. 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/jeffrey2423/commit-like-pro/main/.claude/skills/bmad-help/SKILL.mdgit clone --depth 1 https://github.com/jeffrey2423/commit-like-proWrote 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/jeffrey2423/commit-like-pro/bmad-help)<a href="https://agentmods.dev/skills/jeffrey2423/commit-like-pro/bmad-help"><img src="https://agentmods.dev/badge/skills/jeffrey2423/commit-like-pro/bmad-help/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/jeffrey2423/commit-like-pro/bmad-help"><img src="https://agentmods.dev/badge/skills/jeffrey2423/commit-like-pro/bmad-help.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.00051 | $0.00961 |
| Opus 5.5 | $0.00020 | $0.00384 |
| Sonnet 5.5 | $0.00010 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
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 1mo 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
95% identical to bmad-help — 2 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:
config.yamlanduser-config.yamlfiles in{project-root}/_bmad/and its subfolders — resolveoutput-locationvariables, providecommunication_languageandproject_knowledge - 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.
CSV Interpretation
The catalog uses this format:
module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
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.
- 1mo ago First seen · 76 lines · 51 tokens per session scan A a766c6bd76bc
bmad-help is a skill published in the GitHub repository jeffrey2423/commit-like-pro (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 961 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to bmad-help, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
engineering-principles
Practical engineering judgement: smallest change, subtract before adding, data structures before logic, idempotent operations, migrate callers then delete. Use when designing, building, or reviewing changes.
financial-analysis
Financial figures done carefully: periods and fiscal calendars, units and currencies, reconciliation, magnitude sanity checks, sourced assumptions. Use for statements, budgets, pricing, and diligence numbers.
scheduling
Scheduling across time zones: confirm times in the attendee's own zone, use IANA zone names, mind DST edges, buffers and calendar etiquette. Use when booking meetings or calls with people in other zones.
writing
Writing that sounds human: strip AI tells (em dashes, filler, hype, tacked-on tricolons), plain language, active voice, reader-first structure. Use when drafting or editing copy, docs, posts, or messages.