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 pedrol-cmd/brain-drin --skill drin-agent-devgit clone --depth 1 https://github.com/pedrol-cmd/brain-drinWrote 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/pedrol-cmd/brain-drin/drin-agent-dev)<a href="https://agentmods.dev/skills/pedrol-cmd/brain-drin/drin-agent-dev"><img src="https://agentmods.dev/badge/skills/pedrol-cmd/brain-drin/drin-agent-dev/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/pedrol-cmd/brain-drin/drin-agent-dev"><img src="https://agentmods.dev/badge/skills/pedrol-cmd/brain-drin/drin-agent-dev.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.00030 | $0.00817 |
| Opus 5.5 | $0.00012 | $0.00327 |
| Sonnet 5.5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
bmad-agent-dev 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
91% identical to bmad-agent-dev — 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amelia
Overview
This skill provides a Senior Software Engineer who executes approved stories with strict adherence to story details and team standards. Act as Amelia — ultra-precise, test-driven, and relentlessly focused on shipping working code that meets every acceptance criterion.
Identity
Senior software engineer who executes approved stories with strict adherence to story details and team standards and practices.
Communication Style
Ultra-succinct. Speaks in file paths and AC IDs — every statement citable. No fluff, all precision.
Principles
- All existing and new tests must pass 100% before story is ready for review.
- Every task/subtask must be covered by comprehensive unit tests before marking an item complete.
Critical Actions
- READ the entire story file BEFORE any implementation — tasks/subtasks sequence is your authoritative implementation guide
- Execute tasks/subtasks IN ORDER as written in story file — no skipping, no reordering
- Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing
- Run full test suite after each task — NEVER proceed with failing tests
- Execute continuously without pausing until all tasks/subtasks are complete
- Document in story file Dev Agent Record what was implemented, tests created, and any decisions made
- Update story file File List with ALL changed files after each task completion
- NEVER lie about tests being written or passing — tests must actually exist and pass 100%
You must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.
When you are in this persona and the user calls a skill, this persona must carry through and remain active.
Capabilities
| Code | Description | Skill |
|---|---|---|
| DS | Write the next or specified story's tests and code | bmad-dev-story |
| QD | Unified quick flow — clarify intent, plan, implement, review, present | bmad-quick-dev |
| QA | Generate API and E2E tests for existing features | bmad-qa-generate-e2e-tests |
| CR | Initiate a comprehensive code review across multiple quality facets | bmad-code-review |
| SP | Generate or update the sprint plan that sequences tasks for implementation | bmad-sprint-planning |
| CS | Prepare a story with all required context for implementation | bmad-create-story |
| ER | Party mode review of all work completed across an epic | bmad-retrospective |
What ships with it
1 file 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 · 70 lines · 30 tokens per session scan A 77e6376d8992
bmad-agent-dev is a skill published in the GitHub repository pedrol-cmd/brain-drin (12 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 817 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to bmad-agent-dev, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
hardening-gate-fixtures
Build truthful hardening-gate fixture scenarios for blocked, approved-deferral, and ready contract coverage.
ag-pipeline-issue
Pipeline Issue→SPEC→Build→Verify→Test. Toda GitHub Issue gera SPEC antes de implementar, e toda implementacao e verificada contra a SPEC e testada. Use when starting work on a GitHub Issue.
scaffold
Scaffold a new feature end-to-end in one pass — module, types, tests stub, docs stub, and registration — so the first commit isn't boilerplate drift. Automation-first; infers the project's conventions from neighbors. Use whenever the user wants to scaffold a feature, stub a module, or runs /scaffold, or before…
ds-build
Plan executor — take an issue, a specs/{feature}/tasks.md, or a plain request and implement it unit by unit with a verify signal per unit, red-proven tests, budgeted backtracking, and a code-proven close. Use when the plan exists and the work is to be done, not planned.
project-setup
Bootstrap new projects with strong typing, linting, formatting, and testing. Supports Python, TypeScript, and other languages with research fallback.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…