three-brain

Route Claude outputs to specialized reviewer or rescue models for code review and multimodal analysis.

4|4|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Roentek/Claude_Code_Boilerplate_Framework --skill three-brain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: three-brain
Source: https://github.com/Roentek/Claude_Code_Boilerplate_Framework/tree/main/.claude/skills/three-brain
Command: npx skills add https://github.com/Roentek/Claude_Code_Boilerplate_Framework --skill three-brain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents low-quality self-review by routing Claude’s own outputs into specialized reviewer/rescue models, and it ensures multimodal evidence is extracted with the right preprocessing when media or long documents are involved.

Core Features & Use Cases

  • Forced expert review for Claude’s output: Detects when users ask to “check/review/proof/verify” Claude’s just-produced work and routes the review to Codex instead of performing a blind self-audit.
  • Adversarial risk review on high-blast-radius edits: Triggers Codex adversarial review when an active edit touches sensitive code paths such as auth, billing, migrations, secrets, policy/ACLs, and deployment/IaC concerns.
  • Multimodal handling with preprocessing contracts: Routes video/audio/PDF-heavy requests to Gemini with explicit pipelines (clip/cap duration, extract audio, cap pages, and require timestamped or file/line citations).
  • Failure-counter rescue: Monitors repeated failure patterns and escalates to Codex rescue after defined retries on the same failing operation.
  • High-stakes consensus mode (when explicitly requested): Runs Claude/Codex/Gemini in parallel and enforces a structured adjudication template.

Quick Start

Ask for a second opinion by saying: "Review what you just wrote for bugs and missing tests."

Frequently Asked Questions about three-brain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent Claude from doing a blind self-audit when I ask it to code review its own output?

To prevent ineffective self-review during code review, this Skill detects review verbs like "check" or "verify" and automatically routes Claude's just-produced work to external expert models like Codex for an objective, adversarial analysis instead of a blind self-audit.

What is the best way to trigger adversarial testing on sensitive code paths like auth and billing?

Adversarial testing on sensitive code paths is triggered automatically when an active edit touches high-blast-radius areas such as auth, billing, secrets, or deployment configurations, routing the changes to Codex for specialized risk-path detection and review.

How does multimodal analysis handle video and PDF preprocessing with cited outputs?

Multimodal analysis handles video and PDF preprocessing by routing media-heavy requests to Gemini, applying explicit pipelines that cap duration or pages, extract audio, and enforce structured, evidence-first outputs with timestamps, page numbers, or file/line citations.

Can I escalate code tasks to a rescue model after repeated failure recovery attempts?

Yes, you can escalate tasks to a rescue model after repeated failures; the Skill uses deterministic failure counters to monitor repeated unsuccessful attempts on the same operation and automatically triggers Codex rescue after defined retries.

Does this agent routing approach support high-stakes consensus mode with multiple models?

Yes, high-stakes consensus mode is supported when explicitly requested, running Claude, Codex, and Gemini in parallel to analyze the same task and enforcing a structured adjudication template to resolve differences and verify results.

When should I not use automated expert reviewer routing for my software engineering tasks?

You should avoid automated expert reviewer routing for simple, low-blast-radius edits that do not touch sensitive code paths, as the overhead of invoking external models is unnecessary when standard self-review or basic repo scanning suffices.