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 skyf0xx/hedgehog --skill bmad-forge-ideagit clone --depth 1 https://github.com/skyf0xx/hedgehogWrote 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/skyf0xx/hedgehog/bmad-forge-idea)<a href="https://agentmods.dev/skills/skyf0xx/hedgehog/bmad-forge-idea"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/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/skyf0xx/hedgehog/bmad-forge-idea"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/bmad-forge-idea.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02180 |
| Opus 5 | $0.00028 | $0.01090 |
| Sonnet 5 | $0.00011 | $0.00436 |
| Haiku 4.5 | $0.00006 | $0.00218 |
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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 106 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) are at{bmad-root}/scripts/; this skill's ownresolve_personas.pyis at{skill-root}/scripts/. {workflow.<name>}resolves to fields in the mergedcustomize.toml[workflow]table.{bmad-root}is the vendoredvendor-skills/BMAD/root.
On Activation
- Resolve customization:
uv run {bmad-root}/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). - Resolve
{user_name},{communication_language},{output_folder}using sensible defaults (ask the user or omit{user_name}; English for language fields);{date}is today. Missing values → neutral defaults; never block. Greet{user_name}in{communication_language}and stay in it. - 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.
- 11d ago First seen · 106 lines · 56 tokens per session scan A af002c0b6c58
bmad-forge-idea is a skill published in the GitHub repository skyf0xx/hedgehog (38 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 2,180 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
writing-skills
Use when creating a new skill for the Shipworthy plugin, or when a recurring failure mode needs to be codified into a reusable guide. Covers TDD-for-documentation, CSO (Claude Search Optimization), adversarial testing, and the full skill lifecycle.
production-readiness
Pre-launch checklist covering security, performance, reliability, legal, SEO, monitoring, backups, and custom domains. Each item has both a plain-language explanation and technical implementation detail. Ensures nothing critical is missed before going live.
compliance-awareness
Practical engineering guidance for SOC 2, GDPR, HIPAA compliance and data classification. Covers access controls, audit logging, change management, right to deletion, data portability, consent, PHI encryption, and data classification levels. Engineering checks, not legal advice.
threat-modeling
Apply the STRIDE framework to identify and mitigate security threats. Covers Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege with practical questions, verification steps, and mitigations for each threat category.
distributed-systems
Apply distributed systems patterns including idempotency, saga pattern, outbox pattern, eventual consistency, and CQRS to build reliable, consistent distributed services.
twelve-factor-app
Evaluate and apply the Twelve-Factor App methodology with modern 2025 interpretations. Covers all 12 factors with actionable checks for cloud-native applications running on containers, Kubernetes, and serverless platforms.