design-pipeline: Skill for Claude Code

.agents/skills/bmad-spec/SKILL.md

bmad-spec is a skill for Claude Code, Codex from 2233admin/design-pipeline. It costs 63 tokens per session (3,867 once invoked), scanned A, a copy of bmad-spec, MIT.

A specification-writing tool that turns ideas, notes, documents, or conversations into a clear contract for building software. It records the reason for the work, capabilities, limits, exclusions, and signs of success.

In plain words
What is it for?
Use it to create or update a software specification, validate one, or split it into development stories.
Why use it?
It turns scattered intent into a shared reference that later development work can follow.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is 2233admin/design-pipeline's own configuration. It tells Claude Code and Codex how to work on design-pipeline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything design-pipeline configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/2233admin/design-pipeline/main/.agents/skills/bmad-spec/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/2233admin/design-pipeline

Made for: Claude Code, Codex.

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-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-spec.svg)](https://agentmods.dev/skills/2233admin/design-pipeline/bmad-spec)
Your own site
<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>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,867 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 88% copy Near-identical to another mod 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.00063 $0.03867
Opus 5 $0.00032 $0.01934
Sonnet 5 $0.00013 $0.00773
Haiku 4.5 $0.00006 $0.00387

Measured 8d ago against content hash 5b5680dbf01d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

Origin

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.

.agents/skills/bmad-spec/SKILL.md · 161 lines

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 in customize.toml.

On Activation

  1. Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, read {skill-root}/customize.toml directly.
  2. Run {workflow.activation_steps_prepend}. Treat {workflow.persistent_facts} as foundational context (file: entries are loaded).
  3. 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} (under core), and {date}.
  4. 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 that bmad-party-mode and bmad-advanced-elicitation are available for deeper exploration on any field.

Run {workflow.activation_steps_append}.

Read the full file on GitHub · 161 lines

Files

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.

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. 8d ago First seen · 161 lines · 63 tokens per session scan A 5b5680dbf01d

Subscribe to this mod's changes

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.