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-create-prd/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-create-prd)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-create-prd"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-create-prd.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.00018 | $0.00705 |
| Opus 5 | $0.00009 | $0.00352 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
bmad-create-prd 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
86% identical to bmad-create-prd — 8 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPRECATED — forwards to bmad-prd (create intent)
This skill was consolidated into bmad-prd. It is retained as a thin compatibility shim so existing invocations by name and _bmad/custom/bmad-create-prd.toml override files keep working. New work should invoke bmad-prd directly — it detects create / update / validate intent from the conversation.
On Activation
-
Resolve customization:
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. This picks up any{project-root}/_bmad/custom/bmad-create-prd.tomlandbmad-create-prd.user.tomloverrides for the legacy fields (activation_steps_prepend,activation_steps_append,persistent_facts,on_complete). -
Load
{project-root}/_bmad/bmm/config.yaml(andconfig.user.yamlif present) to resolve{user_name}and{communication_language}. -
Emit a deprecation notice to the user in
{communication_language}:Notice:
bmad-create-prdis deprecated and will be removed in a future release. It now forwards tobmad-prdwith create intent. To silence this notice and access the full new customization surface (prd_template,validation_checklist_template,validation_report_template,doc_standards,finalize_reviewers,external_sources,external_handoffs,prd_output_path,run_folder_pattern), migrate_bmad/custom/bmad-create-prd.tomlto_bmad/custom/bmad-prd.tomland invokebmad-prddirectly next time. Customization fields that were in this version still remain in the new version and will be respected if present in_bmad/custom/bmad-prd.toml, but the new version also supports additional fields that you can take advantage of by migrating. -
Invoke
bmad-prdwith the following context. Pass these as the activating context sobmad-prdhonors them instead of resolving its own customization from scratch:- Intent:
create— skipbmad-prd's usual intent detection step. - Pre-resolved legacy customization — use these in place of resolving from
bmad-prd's owncustomize.tomlfor the four legacy fields. For everything else (prd_template,validation_checklist_template,validation_report_template,doc_standards,finalize_reviewers,prd_output_path,run_folder_pattern,external_sources,external_handoffs), usebmad-prd's own defaults and overrides as normal:activation_steps_prepend= the resolved value from step 1activation_steps_append= the resolved value from step 1persistent_facts= the resolved value from step 1on_complete= the resolved value from step 1
- Original user input: forward whatever the user said when invoking this skill verbatim.
- Intent:
What ships with it
1 file 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.
- 7d ago First seen · 31 lines · 18 tokens per session scan A fa8cc47fff80
bmad-create-prd is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 705 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to bmad-create-prd, differing in 8 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…