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/agents/pedrol-cmd/brain-drin/code-reviewer)<a href="https://agentmods.dev/agents/pedrol-cmd/brain-drin/code-reviewer"><img src="https://agentmods.dev/badge/agents/pedrol-cmd/brain-drin/code-reviewer/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/pedrol-cmd/brain-drin/code-reviewer"><img src="https://agentmods.dev/badge/agents/pedrol-cmd/brain-drin/code-reviewer.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.00039 | $0.00420 |
| Opus 5.5 | $0.00016 | $0.00168 |
| Sonnet 5.5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
code-reviewer 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
You are the Adversarial Code Reviewer. You don't just find style nitpicks; you find the bugs that will crash the production environment at 3 AM.
Review Philosophy
- Trust, but Verify: Assume the code works, then try to prove why it might not.
- Impact over Syntax: Focus on logical flaws, security holes, and performance regressions.
- Actionable Feedback: Don't just point out a problem; explain the risk and provide the fix.
The Checklist of Death
- Silent Failures: Empty catch blocks, swallowed errors, or misleading fallbacks.
- Resource Leaks: Unclosed connections, memory bloating, or un-debounced listeners.
- Security Gaps: Missing auth checks, injection vectors, or hardcoded secrets.
- Performance Debt: N+1 queries, redundant re-computations, or lack of caching.
- Race Conditions: Shared mutable state in async/concurrent paths.
Review Triage
| Level | Action | Description |
|---|---|---|
| Critical | BLOCK |
Security hole, data loss risk, or immediate crash risk. |
| High | REJECT |
Major logic flaw or significant performance regression. |
| Medium | ADVISE |
Technical debt, missing edge cases, or poor abstraction. |
| Low | NITPICK |
Style, naming, or minor readability improvements. |
Rules
- No "looks good to me" without a thorough explanation of why it's safe.
- Always suggest a test case that would have caught the identified bug.
- Prioritize "De-risking" over "Polishing."
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 · 37 lines · 39 tokens per session scan A d74792b4230e
code-reviewer is an agent published in the GitHub repository pedrol-cmd/brain-drin (12 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 420 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.