setup-model-routing
NewInstall the user's standard model-routing setup (Fable 5 orchestrator, deep-reasoner = Opus 4.8 max for architecture research, fast-worker = Sonnet 5 max for execution, gatekeeper = Opus 4.8 max for the acceptance and ship gate, Codex plugin as independent peer engineer) globally on this machine. Use whenever the user mentions 模型分工, model routing, routing hierarchy, fast-worker, deep-reasoner, 双轨 / dual-track, peer engineer setup, or wants to replicate/set up these subagents and the global CLAUDE.md routing section on a new machine — even if they only say "set up my agents" or "同步模型配置".
Summary
This skill installs a three-layer model-routing setup (deep-reasoner, fast-worker, gatekeeper) globally on your machine, enabling efficient delegation of architecture research, implementation, and quality gates to specialized agents.
- It ensures consistent agent configuration across projects and new machines, saving time and reducing errors when replicating your preferred workflow.
Overview
Setup Model Routing
Reproduce the user's standard three-layer model-routing setup. After a successful run, all of the following hold:
- The global Claude home (
$CLAUDE_CONFIG_DIR/agents, default~/.claude/agents) hasfast-worker.md,deep-reasoner.md, andgatekeeper.md(fromassets/) — available in every project. - The global
CLAUDE.md($CLAUDE_CONFIG_DIR/CLAUDE.md, default~/.claude/CLAUDE.md) contains the## Model Routing Hierarchysection. - The codex plugin (
codex@openai-codex) is installed and its readiness check reports"ready": true. - All three agents answer a headless smoke test.
The routing model this installs: Fable 5 plans, delegates, and synthesizes — and exists only in the main loop; every spawned subagent (foreground or background, Agent tool or Workflow) MUST carry an explicit agent type or model override and never inherit Fable (quota constraint). deep-reasoner (Opus, effort: max) executes architecture research, hard reasoning, and judgment-type runs and returns recommendations — opening with RECOMMENDATION: <one sentence> — confidence: HIGH/MEDIUM/LOW — the final framework is always confirmed by the orchestrator; fast-worker (Sonnet, effort: max) executes implementation, tests, refactoring, docs, grading, and mechanical work, reporting RESULT: DONE/PARTIAL/BLOCKED with verification evidence; gatekeeper (Opus, effort: max) is the acceptance and ship gate that reviews delivered work against the goal, runs verification, and returns a PASS/FAIL/BLOCKED ship recommendation — the orchestrator decides, ship actions run only on its explicit execution order, and the gate never fixes code; Codex acts as an independent peer engineer. High-stakes decisions run dual-track: deep-reasoner and Codex produce solutions in parallel without seeing each other, then the main loop compares and decides.
Workflow
Run the installer (installs globally regardless of cwd):
bash ~/.claude/skills/setup-model-routing/scripts/install.shFlags: --project <dir> (project to run the smoke test from, default: cwd — does not change install location), --skip-plugin (no plugin install/check), --skip-smoke (no headless agent test — use in sandboxes without API credentials).
Then read the line-prefixed report and act on it:
- •
[ok]/[new]— nothing to do. - •
[conflict]— a target agent file exists with different content. Never overwrite it: the user may have deliberately customized it. Show the user the diff (the report line contains the exactdiffcommand) and ask whether to keep their version, take the bundled one, or merge. - •
[warn]— a layer could not be verified (missingclaude/node/codexCLI, codex not logged in, smoke test failed). Report the layer as unverified and give the fix:npm install -g @openai/codexfor a missing CLI,!codex loginfor auth (interactive — the user must run it themselves), restart//reload-pluginsfor a session that can't see new agent types yet.
The script exits 0 on success, 3 when any [conflict] was found, 2 on usage errors.
Report format
Summarize per layer, separately — do not collapse into one "done": global agents / global CLAUDE.md / codex plugin / smoke tests. Unverified layers are explicit gaps, not successes. Remind the user that an already-running interactive session loads agent types at startup, so this session won't see newly installed agents until restart or /reload-plugins.
Boundaries
- •Do not edit
~/.claude/rules/ultracode.md— it carries related routing rules but is managed by the user directly. - •Do not enable the codex stop-time review gate; the user positions Codex as a peer engineer, not a mandatory reviewer.
- •Do not "fix" a
[conflict]by overwriting; that path always goes through the user.
Install & Usage
mkdir -p .claude/agentsAdd the configuration to .claude/agents/setup-model-routing.md
@setup-model-routingUse Cases
Usage Examples
/setup-model-routing
Set up my agents on this new machine
同步模型配置
Security Audits
Frequently Asked Questions
What is setup-model-routing?
This skill installs a three-layer model-routing setup (deep-reasoner, fast-worker, gatekeeper) globally on your machine, enabling efficient delegation of architecture research, implementation, and quality gates to specialized agents. It ensures consistent agent configuration across projects and new machines, saving time and reducing errors when replicating your preferred workflow.
How to install setup-model-routing?
To install setup-model-routing: create the agents directory (mkdir -p .claude/agents), then add the config to .claude/agents/setup-model-routing.md. Finally, @setup-model-routing in Claude Code.
What is setup-model-routing best for?
setup-model-routing is a agent categorized under General. It is designed for: agent, plugin. Created by Ancienttwo.
What can I use setup-model-routing for?
setup-model-routing is useful for: Set up the standard model-routing hierarchy on a new machine after cloning your dotfiles or config repo.; Quickly replicate the deep-reasoner, fast-worker, and gatekeeper agents in a fresh Claude Code environment.; Synchronize the global CLAUDE.md routing section and agent files across multiple development machines.; Install the Codex plugin as an independent peer engineer alongside the three routing agents.; Restore the full agent setup after a system reinstall or when onboarding a new team member.; Validate that all routing agents pass smoke tests and the Codex plugin reports ready..