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 ZachArticulateV/designer-pro-and-seo --skill route-three-braingit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/route-three-brain)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/route-three-brain"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/route-three-brain/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/zacharticulatev/designer-pro-and-seo/route-three-brain"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/route-three-brain.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.00100 | $0.00700 |
| Opus 5 | $0.00050 | $0.00350 |
| Sonnet 5 | $0.00020 | $0.00140 |
| Haiku 4.5 | $0.00010 | $0.00070 |
Grade A, and why
route-three-brain 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
route-three-brain
Family: routing Status: Stable
Purpose
The decision layer for cross-model routing. Three models, three roles:
- Claude — primary driver for code, content, design generation, conversation.
- Codex / GPT-5.5 — adversarial review, second-opinion debugging, deep correctness/security checking.
- Gemini — large-context whole-repo analysis, multi-document synthesis, big structured-data passes.
Hard rule: Claude never reviews Claude — same architecture, same blind spots.
If the user says "check your work" / "review this" / "is this right" / "second
opinion" / "sanity check," route to Codex via route-codex-review.
Triggers
- "three brain" / "tri-brain" / "route this" / "which model"
- "delegate to codex" / "delegate to gemini" / "best model for X"
Inputs
- Task description; the current output (if asking for review/handoff)
- Constraints (cost, time, privacy)
Steps
- Startup self-check (once per session). Verify the tools exist:
codex --versionandgemini --version. If one is missing, announce it once and route only to what's available. - Classify the task:
- Build/generate/converse → Claude keeps it.
- Review / verify / debug a substantial output, or any risk-path edit (auth,
billing, migrations, deploy, secrets) → Codex via
route-codex-review. - Needs more context than one window (whole repo, many docs) → Gemini via
route-gemini-context.
- Announce forced routes in one line before running (so the user can interrupt):
[three-brain] routing to Codex (review) — risk path: src/auth/. - Execute the handoff via the execution skills and integrate the result — diff where models agree/disagree and adjudicate by evidence, not by averaging.
Outputs
- A routing decision with justification
- The integrated result of any executed handoff
Dependencies
route-codex-review(Codex execution),route-gemini-context(Gemini execution)- The
codexandgeminiCLIs installed (or the adjacentopenai-codex/cc-gemini-plugintools); degrades to a recommendation when neither is present
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.
- 12d ago First seen · 66 lines · 100 tokens per session scan A 781012093ef6
route-three-brain is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 700 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…
engineering-onboarding
Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…