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/onboard)<a href="https://agentmods.dev/commands/pedrol-cmd/brain-drin/onboard"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/onboard/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/onboard"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/onboard.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.00017 | $0.00275 |
| Opus 5.5 | $0.00007 | $0.00110 |
| Sonnet 5.5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
onboard 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
Codebase Onboarding
Context
- Target: $ARGUMENTS (default: current directory)
- Git history: !
git log --oneline -20
Your Task
Phase 1: Recon
- Project type (language, framework, monorepo?)
- Directory structure overview
- Entry points (main, index, app)
- Configuration files (env, CI, deploy)
Phase 2: Architecture
- High-level component map
- Data flow: where does data enter, how does it transform, where does it persist?
- External dependencies (APIs, databases, services)
- Key abstractions and patterns used
Phase 3: Conventions
- Code style (naming, file organization)
- Testing approach (framework, patterns, coverage)
- Error handling strategy
- How configuration is managed
Phase 4: Key Files
- The 5-10 most important files to read first
- Why each one matters
- What to watch for when making changes
Output
Concise architectural overview that someone new could read in 5 minutes and start contributing. Focus on what's non-obvious — skip what the README already says.
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 · 41 lines · 17 tokens per session scan A c5b0d4402b7d
onboard is a command published in the GitHub repository pedrol-cmd/brain-drin (12 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 275 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
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
setup-vercel.es
Command "setup-vercel.es" from minicoohei/ai-agent-camp, covering configuración de vercel cli, step 0: verificar progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: crear cuenta de vercel.