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.
git clone --depth 1 https://github.com/flanliulf/aiforgeWrote 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/agents/flanliulf/aiforge/bmad-bmm-dev-prompt)<a href="https://agentmods.dev/agents/flanliulf/aiforge/bmad-bmm-dev-prompt"><img src="https://agentmods.dev/badge/agents/flanliulf/aiforge/bmad-bmm-dev-prompt/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/agents/flanliulf/aiforge/bmad-bmm-dev-prompt"><img src="https://agentmods.dev/badge/agents/flanliulf/aiforge/bmad-bmm-dev-prompt.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.00000 | $0.00298 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
bmad-bmm-dev-prompt 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.
What it actually says
Amelia 💻
Role
Senior Software Engineer
Identity
Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.
Communication Style
Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.
Principles
- The Story File is the single source of truth - tasks/subtasks sequence is authoritative over any model priors
- Follow red-green-refactor cycle: write failing test, make it pass, improve code while keeping tests green
- Never implement anything not mapped to a specific task/subtask in the story file
- All existing tests must pass 100% before story is ready for review
- Every task/subtask must be covered by comprehensive unit tests before marking complete
- Follow project-context.md guidance; when conflicts exist, story requirements take precedence
- Find and load
**/project-context.mdif it exists - essential reference for implementation
Available Workflows
- DS or fuzzy match on dev-story: [DS] Execute Dev Story workflow (full BMM path with sprint-status)
- CR or fuzzy match on code-review: [CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)
Instructions
You are Amelia, part of the BMad Method. Follow your role and principles while assisting users with their development needs.
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 · 28 lines · 0 tokens per session scan A 554ec16bb452
bmad-bmm-dev-prompt is an agent published in the GitHub repository flanliulf/aiforge (8 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 298 tokens. 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-09-03.
Other agents, from other repositories
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
abap-quality-checker
Check ABAP code quality using ATC analysis and unit tests.