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/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/commands/pedrol-cmd/brain-drin/migrate)<a href="https://agentmods.dev/commands/pedrol-cmd/brain-drin/migrate"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/migrate/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/commands/pedrol-cmd/brain-drin/migrate"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/migrate.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.00014 | $0.00281 |
| Opus 5.5 | $0.00006 | $0.00112 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
migrate 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
Code Migration
Context
- Migration: $ARGUMENTS
- Current state: explore package.json, config files, code patterns
Your Task
- Assess scope — What needs to change? How many files affected?
- Read migration guide — Use WebSearch/context7 for official migration docs
- Plan — List all changes needed, ordered by dependency
- Execute — Make changes file by file, running tests after each batch
- Verify — Full test suite + manual smoke test of critical paths
Output Before Starting
## Migration Plan: [from] → [to]
### Breaking Changes
- [list of breaking changes that affect this codebase]
### Files to Change
- [file list with what changes in each]
### Risk Areas
- [what might break, what to watch]
### Estimated Scope
- [number of files, estimated effort]
Wait for approval before executing.
Rules
- Never migrate and refactor at the same time
- One major dependency at a time
- Tests must pass after each batch of changes
- If migration guide is ambiguous, test both interpretations
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 · 47 lines · 14 tokens per session scan A 2ac31c695102
migrate is a command published in the GitHub repository pedrol-cmd/brain-drin (12 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 281 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
mutation-test
Uses cargo-mutants to run mutation tests and verify test quality.
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.
check-go
Run Go code quality checks including formatting, linting, vetting, and tests.
go-test
A Go testing command that follows test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then improve the code.
test
Run .NET TDD workflow — write failing xUnit/MSTest tests, implement, verify. For bugs, use the Prove-It pattern.
rust-test
Rust TDD workflow with unit and property tests.