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-spec/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-spec)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-spec"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-spec.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.00063 | $0.03867 |
| Opus 5 | $0.00032 | $0.01934 |
| Sonnet 5 | $0.00013 | $0.00773 |
| Haiku 4.5 | $0.00006 | $0.00387 |
Grade A, and why
bmad-spec 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 8d 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
88% identical to bmad-spec — 21 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMad Spec
Overview
Canonical transformer for the BMad spec-kernel ecosystem. Takes any intent input — vague idea, brain dump, PRD, GDD, RFC, brief, Slack thread, customer email, meeting transcript, mockups, mixed multi-source — and produces SPEC.md carrying the five-field kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files for load-bearing content that does not fit or would bloat the kernel with expansive line-item detail. Together they are the machine contract every downstream BMad skill consumes.
Multiple skills may call to update the same spec over time.
Conventions
- Bare paths (e.g.
assets/spec-template.md) resolve from the skill root. {skill-root}is this skill's install dir;{project-root}is the working dir.{workflow.<name>}resolves to fields incustomize.toml.
On Activation
- Resolve customization:
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, read{skill-root}/customize.tomldirectly. - Run
{workflow.activation_steps_prepend}. Treat{workflow.persistent_facts}as foundational context (file:entries are loaded). - Resolve config:
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}(merges_bmad/config.toml,_bmad/config.user.toml, and the_bmad/custom/overrides). From the merged JSON resolve{user_name},{communication_language},{document_output_language},{project_name},{output_folder}(undercore), and{date}. - Detect mode. Headless when any of: no TTY, programmatic caller (another skill or non-interactive runner), or the first message pre-supplies all inputs and asks for an artifact path back. Interactive otherwise. In interactive mode, greet by
{user_name}in{communication_language}, stay in that language, and mention thatbmad-party-modeandbmad-advanced-elicitationare available for deeper exploration on any field.
Run {workflow.activation_steps_append}.
What ships with it
4 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.
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.
- 8d ago First seen · 161 lines · 63 tokens per session scan A 5b5680dbf01d
bmad-spec is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 3,867 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to bmad-spec, differing in 21 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.
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
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…