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 zsutxz/ClaudeLearning --skill bmad-module-buildergit clone --depth 1 https://github.com/zsutxz/ClaudeLearningWrote 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/zsutxz/claudelearning/bmad-module-builder)<a href="https://agentmods.dev/skills/zsutxz/claudelearning/bmad-module-builder"><img src="https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-module-builder/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/zsutxz/claudelearning/bmad-module-builder"><img src="https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-module-builder.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.00045 | $0.00606 |
| Opus 5 | $0.00023 | $0.00303 |
| Sonnet 5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
bmad-module-builder 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
100% identical to bmad-module-builder — 0 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMad Module Builder
Overview
This skill helps you bring BMad modules to life — from the first spark of an idea to a fully scaffolded, installable module. It offers three paths:
- Ideate Module (IM) — A creative brainstorming session that helps you imagine what your module could be, decide on the right architecture (agent vs. workflow vs. both), and produce a detailed plan document. The plan then guides you through building each piece with the Agent Builder and Workflow Builder.
- Create Module (CM) — Takes an existing folder of built skills (or a single skill) and scaffolds the module infrastructure that makes it installable. For multi-skill modules, generates a dedicated
-setupskill. For single skills, embeds self-registration directly into the skill. Supports--headless/-H. - Validate Module (VM) — Checks that a module's structure is complete and correct — every skill has its capabilities registered, entries are accurate and well-crafted, and structural integrity is sound. Handles both multi-skill and standalone modules. Supports
--headless/-H.
Args: Accepts --headless / -H for CM and VM paths, an initial description for IM, or a path to a skills folder or single SKILL.md file for CM/VM.
On Activation
Load available config from {project-root}/_bmad/config.yaml and {project-root}/_bmad/config.user.yaml (root level and bmb section). If neither exists, fall back to {project-root}/_bmad/bmb/config.yaml (legacy per-module format). If still missing, let the user know bmad-builder-setup can configure the module at any time. Use sensible defaults for anything not configured.
Detect user's intent:
- Ideate / Plan keywords or no path argument → Load
./references/ideate-module.md - Create / Scaffold keywords, a folder path, or a path to a single SKILL.md file → Load
./references/create-module.md - Validate / Check keywords → Load
./references/validate-module.md - Unclear → Present options:
- Ideate Module (IM) — "I have an idea for a module and want to brainstorm and plan it"
- Create Module (CM) — "I've already built my skills and want to package them as a module"
- Validate Module (VM) — "I want to check that my module's setup skill is complete and correct"
What ships with it
19 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.
- assets/module-plan-template.md 4.3 KB
- assets/setup-skill-template/assets/module-help.csv 123 B
- assets/setup-skill-template/assets/module.yaml 96 B
- assets/setup-skill-template/scripts/cleanup-legacy.py 8.7 KB runs code
- assets/setup-skill-template/scripts/merge-config.py 15 KB runs code
- assets/setup-skill-template/scripts/merge-help-csv.py 7.6 KB runs code
- assets/setup-skill-template/SKILL.md 8.2 KB
- assets/standalone-module-template/merge-config.py 15 KB runs code
- assets/standalone-module-template/merge-help-csv.py 7.6 KB runs code
- assets/standalone-module-template/module-setup.md 6.6 KB
- references/create-module.md 17 KB
- references/ideate-module.md 18 KB
- references/validate-module.md 5.6 KB
- scripts/scaffold-setup-skill.py 3.9 KB runs code
- scripts/scaffold-standalone-module.py 6.0 KB runs code
- scripts/tests/test-scaffold-setup-skill.py 7.9 KB runs code
- scripts/tests/test-scaffold-standalone-module.py 9.3 KB runs code
- scripts/tests/test-validate-module.py 19 KB runs code
- scripts/validate-module.py 14 KB runs code
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 · 33 lines · 45 tokens per session scan A 344ee5a89587
bmad-module-builder is a skill published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 606 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bmad-module-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…