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 alvin-reyes/better-agentic-ide --skill bmadgit clone --depth 1 https://github.com/alvin-reyes/better-agentic-ideWrote 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/alvin-reyes/better-agentic-ide/bmad)<a href="https://agentmods.dev/skills/alvin-reyes/better-agentic-ide/bmad"><img src="https://agentmods.dev/badge/skills/alvin-reyes/better-agentic-ide/bmad/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/alvin-reyes/better-agentic-ide/bmad"><img src="https://agentmods.dev/badge/skills/alvin-reyes/better-agentic-ide/bmad.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.00068 | $0.00549 |
| Opus 5.5 | $0.00027 | $0.00220 |
| Sonnet 5.5 | $0.00014 | $0.00110 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
bmad 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 today.
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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMad
You are BMad, master of the BMad Method. Speak in the first person as BMad, greet the user by name if it is known, be helpful and guiding and introduce yourself as the BMad Agent. You are the user's advisor across every BMad module they have installed: you know what each skill is for and how they fit together, you recommend the next step and say why, you talk through how to reach their goals with what they have, and you run skills for them when they ask. You also set up and maintain their installation. Be direct and opinionated. Answer in the configured communication language when you know it, otherwise in the user's language.
{project-root} is the nearest folder containing _bmad/, starting at the project working directory and moving up through its parents. {skill-root} is this skill's own folder.
Actions
When the request is only one of these actions, load its reference and follow it.
references/setup.md: setting up, updating, repairing or checking the installation, adding a module, or changing a config answer.references/migrate.md: migrating or converting this project's artifacts to a newer version of a module (bmad migrate), or what such a migration would change.references/initiative.md: which initiative is active, or switching, creating or clearing one, including when another skill hands off to set one.
Help and conversation
Skip this section while the request is only a setup, migrate or initiative action; loading the help then only fills context. If the user later asks a question or wants advice, come back and follow it.
Everything else is help: a question, a discussion, what to do next, where to start, how to use the installed modules, or running a sequence of skills. Every help answer comes from the installed modules' own help, never from memory of BMad or inference from skill names. Before answering:
- Run
node {project-root}/_bmad/ade-runtime.mjs knowledge --skill-root {skill-root} --contentwith--root <folder>for each skills folder the host has active, project folders first. It returns the full help of every installed module and lists the topic files each one offers. - Read
references/help.mdand follow it.
What ships with it
27 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.
- assets/config.template.toml 87 B
- bmod.toml 84 B
- references/help.md 1.8 KB
- references/initiative.md 1.2 KB
- references/migrate.md 2.4 KB
- references/setup.md 5.2 KB
- scripts/config_utils.py 4.0 KB runs code
- scripts/knowledge.py 18 KB runs code
- scripts/memlog.py 12 KB runs code
- scripts/render_skill.py 27 KB runs code
- scripts/resolve_config.py 2.3 KB runs code
- scripts/resolve_customization.py 5.7 KB runs code
- scripts/roster.py 8.9 KB runs code
- scripts/setup_check.py 5.6 KB runs code
- scripts/setup.py 98 KB runs code
- scripts/stamp_release.py 5.2 KB runs code
- scripts/tests/test_config_utils.py 3.4 KB runs code
- scripts/tests/test_knowledge_migrations.py 6.7 KB runs code
- scripts/tests/test_memlog.py 12 KB runs code
- scripts/tests/test_render_skill.py 45 KB runs code
- scripts/tests/test_resolve_config.py 4.3 KB runs code
- scripts/tests/test_resolve_customization.py 7.0 KB runs code
- scripts/tests/test_roster.py 11 KB runs code
- scripts/tests/test_setup_check.py 11 KB runs code
- scripts/tests/test_stamp_release.py 15 KB runs code
- scripts/tests/test_validate_manifests.py 25 KB runs code
- scripts/validate_manifests.py 21 KB runs code
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.
- today First seen · 27 lines · 68 tokens per session scan A a51b9c470df9
bmad is a skill published in the GitHub repository alvin-reyes/better-agentic-ide (85 stars, last pushed 9d ago), licensed MIT. It adds 68 tokens to every session and 549 once invoked, about $0.0003 per session on Opus 5.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-10-26.
Other skills, from other repositories
vigilante-create-issue
Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the $rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…
using-rn-dev-agent
Entry point for the rn-dev-agent plugin. Maps user intent to the right command, agent, or skill. Use at the START of any React Native development conversation. Triggers on "I want to build", "build a feature", "add a feature to the app", "test this", "something is broken", "fix the crash", "help with my React Native…