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-forge-ideagit 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-forge-idea)<a href="https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-forge-idea"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-forge-idea/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-forge-idea"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-forge-idea.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.00056 | $0.02246 |
| Opus 5.5 | $0.00022 | $0.00898 |
| Sonnet 5.5 | $0.00011 | $0.00449 |
| Haiku 4.5 | $0.00006 | $0.00225 |
Grade A, and why
bmad-forge-idea 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
89% identical to bmad-forge-idea — 4 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMad Forge Idea
Overview
Take a half-formed idea and pressure-test it in conversation, while changing your mind is still cheap, until it becomes something the user can act on with conviction or reject. The main risk is what the user has not examined yet: unchecked assumptions and unresolved decisions usually become more expensive problems later.
The main goal is better thinking, not producing an artifact. Strengthening an idea, rejecting it, or thinking it through more clearly are all complete outcomes. Writing forged-idea.md to hand off to another workflow is optional. Do not steer the conversation toward "shall we build it?"
This skill can be used on many kinds of ideas. When the idea is about a product or feature, what survives may be written to forged-idea.md for later planning.
Lead by questioning, not lecturing. Ask one question at a time, press on weak points, and do not let vague claims pass without examination.
Conventions
- Scripts live in two places — run each from the exact path written, never assume co-location: the shared core scripts (
memlog.py,resolve_customization.py,resolve_config.py) are installed by BMad core at{project-root}/_bmad/scripts/and are never bundled here; this skill's ownresolve_personas.pyis at{skill-root}/scripts/. {workflow.<name>}resolves to fields in the mergedcustomize.toml[workflow]table.
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 with defaults. Apply the resolved{workflow.*}values throughout. - Run each
{workflow.activation_steps_prepend}entry; treat each{workflow.persistent_facts}entry as foundational context (file:entries load their contents,skill:names a skill to consult, others are facts verbatim). - Load
{project-root}/_bmad/core/config.yaml(andconfig.user.yamlif present); resolve{user_name},{communication_language},{output_folder}. Missing → neutral defaults; never block. Greet{user_name}in{communication_language}and stay in it. - Note whether a BMad persona is already active in this conversation — the user loaded one (e.g. the analyst, the storyteller) and invoked the forge from within it. If so, that persona leads the session, in voice, throughout.
- Resume: glob
{workflow.forge_output_path}/**/.memlog.md(recursive, so it still finds sessions whenrun_folder_patternis overridden to nest paths) and read only each match's frontmatter to find any whosestatusis notcomplete. Offer to resume one — then read its full memlog once to rebuild state and continue append-only — or to start fresh. - Run each
{workflow.activation_steps_append}entry.
What ships with it
3 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.
- 1mo ago First seen · 108 lines · 56 tokens per session scan A c62ac3a30a4c
bmad-forge-idea is a skill published in the GitHub repository mmornati/leanproxy-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,246 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to bmad-forge-idea, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).