agentmods.dev

bmad-workflow-builder

bmad-workflow-builder is a skill for Claude Code from zsutxz/ClaudeLearning. It costs 44 tokens per session (1,035 once invoked), scanned A, original, MIT.

A workflow-building assistant for creating, editing, checking, and analyzing coding-agent workflows and skills.

In plain words
What is it for?
It is for building new workflows, modifying existing skills, checking their quality, and analyzing how they work.
Why use it?
It helps turn an incomplete idea into clearer instructions that an agent can follow consistently.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

not rated 5repo 1mo ago A scan 44 tokens original MIT

Good fit It is for building new workflows, modifying existing skills, checking their quality, and analyzing how they work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zsutxz/claudelearning/bmad-workflow-builder
View source ↗ zsutxz/ClaudeLearning
Install

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.

Any agent
npx skills add zsutxz/ClaudeLearning --skill bmad-workflow-builder
Clone the repo
git clone --depth 1 https://github.com/zsutxz/ClaudeLearning

Made for: Claude Code.

Wrote 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.

agentmods badge for bmad-workflow-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-workflow-builder/github.svg)](https://agentmods.dev/skills/zsutxz/claudelearning/bmad-workflow-builder)
Your own site
<a href="https://agentmods.dev/skills/zsutxz/claudelearning/bmad-workflow-builder"><img src="https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-workflow-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.

agentmods 80×15 button for bmad-workflow-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/zsutxz/claudelearning/bmad-workflow-builder"><img src="https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-workflow-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,035 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01035
Opus 5 $0.00022 $0.00517
Sonnet 5 $0.00009 $0.00207
Haiku 4.5 $0.00004 $0.00103

Measured 9d ago against content hash ed28d89b38b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

bmad-workflow-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 9d ago.

The scan reads SKILL.md. This mod also ships 11 executable files (scripts/count_tokens.py, scripts/init_skill.py, scripts/prepass-prompt-metrics.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/bmad-workflow-builder/SKILL.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Act as a skill-building partner who turns a half-formed idea in the user's head into a lean, outcome-driven skill. Every line in what you build has to earn its place against one test: would a capable model do this correctly without being told? If the answer is yes, the line is friction and it stays out. You model the shape you teach, so this skill's own build flow is a goal-driven loop rather than a fixed sequence of phases.

Args: --headless / -H for non-interactive; an initial description for a new build; or a path to an existing skill alongside words like analyze, edit, or rebuild. To re-shape an existing non-BMad skill, point at it and say what should change, and the build flow takes it from there.

Resolution rules

  • Bare paths and {skill-root} (e.g. references/foo.md or {skill-root}/assets/bar.csv) resolve from this skill's installed directory — not the project directory.
  • {project-root} → the project working directory.
  • {target-skill-path} → the skill being built, edited, or analyzed.

On Activation

  1. Resolve customization. Run uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow and apply the resolved {workflow.*} values throughout the session. On failure, read {skill-root}/customize.toml directly and use defaults. Then execute each entry in {workflow.activation_steps_prepend} in order, and treat every entry in {workflow.persistent_facts} as standing context for the whole session (entries prefixed file: are paths or globs whose contents load as facts, skill: names a skill to consult, all others are literal facts).

  2. Detect intent. If --headless or -H is present, set {headless_mode}=true for every sub-prompt. Otherwise read the invocation for whether the user wants to Build, Edit, or Analyze, and which skill they mean.

  3. Load config. Read {project-root}/_bmad/config.yaml and {project-root}/_bmad/config.user.yaml (root and bmb section), falling back to {project-root}/_bmad/bmb/config.yaml. If none exist and bmad-bmb-setup is available, mention it. Resolve and apply throughout (defaults in parens): {user_name} (null), {communication_language} (user or system default), {document_output_language} (user or system default), and {bmad_builder_output_folder} ({project-root}/skills, where new skills are created; existing skills keep their own path).

Read the full file on GitHub · 43 lines

Files

What ships with it

33 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.

Changes

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.

  1. 9d ago First seen · 43 lines · 44 tokens per session scan A ed28d89b38b1

Subscribe to this mod's changes

bmad-workflow-builder is a skill published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,035 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-09-03.

Building agentsPlanning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens