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 mmornati/leanproxy-mcp --skill bmad-create-prdgit clone --depth 1 https://github.com/mmornati/leanproxy-mcpWrote 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/mmornati/leanproxy-mcp/bmad-create-prd)<a href="https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-create-prd"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-create-prd/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/mmornati/leanproxy-mcp/bmad-create-prd"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-create-prd.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.00035 | $0.00701 |
| Opus 5.5 | $0.00014 | $0.00280 |
| Sonnet 5.5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
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 1mo 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-create-prd — 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 — 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:
python3 {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,doc_standards,external_sources,external_handoffs,output_dir,output_folder_name), 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,validation_report_template,doc_standards,output_dir,output_folder_name,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.
- 1mo ago First seen · 31 lines · 35 tokens per session scan A 143c5c2d8573
bmad-create-prd is a skill published in the GitHub repository mmornati/leanproxy-mcp (5 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 701 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to bmad-create-prd, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
go
Use when writing, reviewing, testing, or shipping Go code and HTTP services: idioms, %w error wrapping, goroutine/context/errgroup concurrency, net/http 1.22 routing, log/slog, project layout, table-driven tests, Go hardening. NOT language-agnostic threat modeling (that is secure-coding), NOT Dockerfile/CI shipping…
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.
nightly-session-watch
Nightly sweep of the last 24h of pi-go sessions — anomalous runs, loop aborts, tool error rates, token waste, real prompt-token spend, and whether the observation and palace pipelines are still recording. Triages each finding to the specialist skill that diagnoses it. Use for an unattended daily health check, or on…
memory-mine
Mine project files or conversations into the MemPalace memory system. Indexes source code and conversation history as searchable palace drawers with semantic embeddings and room assignment.