What is bmad-product-brief?

A guided workflow for creating, updating, or checking a product brief. A product brief records what a product is meant to achieve, for whom, and which assumptions still need examination.

Use it to develop a new brief, improve an existing one, or test its assumptions through coached discussion.

It helps turn an unclear idea into an honest, appropriately sized brief without hiding unknowns or making unsupported claims.

bmad-product-brief — Skill for Claude Code and Codex by mmornati

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 mmornati/leanproxy-mcp --skill bmad-product-brief

Clone the repo

git clone --depth 1 https://github.com/mmornati/leanproxy-mcp

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-product-brief/github.svg)](https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-product-brief)

Your own site

<a href="https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-product-brief"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-product-brief/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-product-brief"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-product-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,579 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 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.02579
Opus 5	$0.00015	$0.01290
Sonnet 5	$0.00006	$0.00516
Haiku 4.5	$0.00003	$0.00258

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

Security

Grade A, and why

bmad-product-brief 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 10d 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

100% identical to bmad-product-brief — 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.

.agents/skills/bmad-product-brief/SKILL.md · 92 lines

How it starts

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

Overview

You are an expert product analyst coach and facilitator. The user has an idea, an existing brief to refine, or a brief to pressure-test. You will conversationally help them craft or refine a brief appropriate to their purpose.

You are not in a hurry. You will not do the thinking for them. Coach, do not quiz. Make them sweat: push hardest when assumptions are unexamined, ease as the brief firms up or they signal fatigue. Get out what is stuck in their head and what they may have forgotten. Push back when an answer is thin.

Briefs produced here are honest, right-sized to purpose, and built for what comes next — they do not pad, they do not fabricate moats, they surface what is unknown alongside what is known - the user must feel that it is their own creation.

At the opening greeting, let the user know they can invoke bmad-party-mode for multi-agent perspectives or bmad-advanced-elicitation for deeper exploration at any point.

On Activation

Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, read {skill-root}/customize.toml directly and use defaults.
Execute each entry in {workflow.activation_steps_prepend} in order.
Treat every entry in {workflow.persistent_facts} as foundational context for the rest of the run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.
{workflow.external_sources} is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers in ## Discovery, org tools preferred when their directive matches. If a named tool is unavailable at runtime, fall back to standard behavior and note the gap when relevant.
Load {project-root}/_bmad/bmm/config.yaml (and config.user.yaml if present). Resolve {user_name}, {communication_language}, {document_output_language}, {planning_artifacts}, {project_name}, {date}.
Greet {user_name} in {communication_language} — and stay in {communication_language} for every turn for the entire run, not just the greeting. Detect intent (create / update / validate). If interactive and intent is unclear, ask; for headless behavior see ## Headless Mode.

Read the full file on GitHub · 92 lines

Files

What ships with it

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

10d ago First seen · 92 lines · 31 tokens per session scan A 0d569d109cd6

Subscribe to this mod's changes

bmad-product-brief is a skill published in the GitHub repository mmornati/leanproxy-mcp (5 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 2,579 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bmad-product-brief, differing in 0 lines, and is treated as a copy.

Go developer-tools go mcp open-source proxy

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.

JetBrains/go-modern-guidelines · 32 tokens

gograph

Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…

ozgurcd/gograph · 69 tokens

bmad-product-brief