pvjbuilds/delegate-router / skills/delegate
delegate
VerifiedHand bulky, already-decided implementation work from the agent you are working in (Claude Code or Codex CLI) to another paid model: Codex (GPT models), Gemini via the Antigravity `agy` CLI, or a Claude Opus subagent. Saves the main session's quota and context. Picks the model from ROUTING.md unless the user names one, and never routes back to the host's own model (except an Opus subagent under an Opus host, which keeps the main context clean). Use for mechanical, large work: scaffolding, boilerplate, repetitive edits across many files, test stubs, docstrings, format conversions, a fully specified function or module, or bulk reading of media and long documents. Also use when the user says /delegate, "delegate this", "send this to Codex/Gemini/Claude", or "don't burn tokens on this". The host always plans, specs and verifies; the delegate only types. Do NOT delegate debugging, architecture, cross-file refactors, security code, anything subtle, or work under ~40 lines.
| File | Kind | Size |
|---|---|---|
| ROUTING.md | markdown | 9.2 KB |
| SKILL.md | skill md | 11.7 KB |
| scripts/jev.py | script | 9.5 KB |
| scripts/model_watch.py | script | 35.3 KB |
ROUTING.md
View on GitHub# Routing map: which model gets which task
Snapshot: 2026-11-20
The delegate skill reads this file to pick a model. Benchmarks are a prior, not proof: **a
check run on the actual task beats any benchmark.** Neutral benchmarks pick a new model's
first route; before it takes that route, the maintainer runs it through the bench (`bench/` in the repo
root) against the model that holds the route now. History: 2026-09-30 said "don't run trial
calls to confirm them". 2026-10-27 the maintainer changed it to bench each new model on
routine tasks.
`git pull` in the repo brings a newer snapshot. `model_watch.py status` says when this file
is more than 60 days old or when your CLIs list a model it doesn't cover yet.
## How to read a row
Walk the candidates in order and take the first one that:
1. **is installed** (`model_watch.py status` lists the CLIs),
2. **is not the host's own model.** Same model, same quota: no gain. One exception: inside
Claude Code, the `opus-implementer` subagent is allowed even when the host is Opus,
because it keeps the file reads and tool turns out of the main context, and
3. **runs on another subscription than the host**, when the row has one installed. The
subscription goes by CLI: `codex` is the OpenAI plan, `claude` and `opus-implementer` the
Anthropic plan, `agy` the Google plan. This spreads the work across the plans you pay for.
If no candidate on another plan is installed, take the first one on the host's plan and say
so in one line.
Two rows skip rule 3 and walk in plain order:
- **Must be right**: correctness matters more than quota.
- **Trivial edits**: a rename isn't worth a stronger model's quota; the cheap model stays first
even on the host's plan.
If nothing in a row qualifies, the host does the work itself.
## Default route
| Task | Candidates, in order | CLI and model ID | Effort |
|---|---|---|---|
| **Bulk code** from a written spec: new module, boilerplate, test stubs, many-file mechanical edits | 1. GPT-6.1 Terra<br>2. GPT-6.2 Sol<br>3. Claude Opus 5.5 | `codex` · `gpt-6.1-terra`<br>`codex` · `gpt-6.2-sol`<br>`opus-implementer` · `claude-opus-5-5` | medium<br>medium<br>medium |
| **Must be right**: correctness matters more than quota, terminal-heavy agent work, or a spec the first pick already failed | 1. Claude Opus 5.5<br>2. GPT-6.2 Sol | `opus-implementer` · `claude-opus-5-5`<br>`codex` · `gpt-6.2-sol` | medium<br>medium |
| **Trivial edits**: reformatting, renames, mechanical find-and-replace | 1. GPT-6 Luna<br>2. Claude Opus 5.5 | `codex` · `gpt-6-luna`<br>`opus-implementer` · `claude-opus-5-5` | medium<br>medium |
| **Images**: screenshots, scanned pages, charts (image files) | 1. GPT-6.1 Terra<br>2. Gemini 3.8 Flash | `codex exec -i <file>` · `gpt-6.1-terra`<br>`agy` · `gemini-3.8-flash-high` | medium<br>(in the ID) |
| **Media and long reads**: PDF, video, audio, long documents | 1. Gemini 3.8 Flash<br>2. Claude Opus 5.5 | `agy` · `gemini-3.8-flash-high`<br>`opus-implementer` · `claude-opus-5-5` | (in the ID)<br>medium |
| **Single-file text** with no repo access: a conversion, a fixture, a draft | 1. Gemini 3.8 Flash<br>2. GPT-6.2 Sol | `agy` · `gemini-3.8-flash-high`<br>`codex` · `gpt-6.2-sol` | (in the ID)<br>medium |
| **Hard reasoning**: maths, proofs, algorithms, science, very large documents | 1. GPT-6.2 Astra | `codex` · `gpt-6.2-astra` | low, raise only if needed |
| **Review**: security review, second opinion on a design or a diff | 1. GPT-6.2 Astra (read-only)<br>2. Claude Opus 5.5 (read-only) | `codex -s read-only` · `gpt-6.2-astra`<br>`claude -p --restricted` · `claude-opus-5-5` (SKILL.md has the full command) | low<br>medium |
**Quota out.** A usage-limit error usually names its reset time. Say it in one line and fall
through to the next candidate; don't stall. If a CLI call fails, report that model as
missing, never quietly drop it.
## Why these picks
In our own words; the numbers live on the trackers linked at the bottom.
- **GPT-6.1 Terra** is the default typist since 2026-11-01, the maintainer's pick to spend
fewer tokens. On our bench (`bench/`) it passed 10/10 on 2026-10-27, as GPT-6.1 Sol high did,
on fewer tokens. It runs on the Codex plan's separate quota. After a failed run, escalate to
GPT-6.2 Sol, then Opus, rather than retrying Terra.
- **GPT-6.2 Sol at medium** is the second typist since 2026-11-20 (the maintainer's pick). At
medium it scores above GPT-6.1 Sol at high on independent intelligence indexes and answers
much faster. On our bench it passed 10/10 for about $0.09 per task with cached input priced in,
a couple of cents more than GPT-6.1 Sol high. It takes over when Terra fails a packet.
- **Claude Opus 5.5 at medium effort** is the must-be-right choice and the fallback for
everything. It leads on agentic tool use and production software engineering. Medium is its
knee: each step up costs much more per point gained.
- **Claude Sonnet 5.5 is not routed.** It is cheaper per token but uses far more tokens, so it
costs more per task at equal quality. **Compare cost per task, not price per token.**
- **GPT-6.2 Astra** leads on maths, science, abstract reasoning, very long-context retrieval and
security work. It is slow and expensive, so it gets hard problems and reviews, not bulk typing.
It replaced GPT-6 Astra on 2026-11-20: higher on independent intelligence indexes at every
effort, a lower price per token, and on our bench it passed the same tasks for less per task.
- **GPT-6.1 Sol** is replaced by GPT-6.2 Sol (2026-11-20).
- **Gemini 3.8 Flash** is fast and cheap, and strong at video and other media. It is weak at
multi-step agent work, so it runs in plan mode and only its text output is used.
- **GPT-6.1 Terra** also reads images. Independent multimodal scores put it at or near the top
of the field, and it is cheap per task.
`codex exec -i` takes image files only, so PDF, video and audio stay with Gemini.
- **GPT-6 Luna** is very cheap and fast but clearly weaker. Mechanical edits only.
- **Not routed:** Claude Haiku 5.5 (`claude-haiku-5-5`; the strongest small model, but very
verbose and it spends the Claude quota that cheaper Codex and Gemini tiers spare), Claude
Haiku 4.5 (replaced by Haiku 5.5), Claude Fable 5.1 (Opus 5.5 scores higher and costs less),
older GPT and Gemini tiers.
## Rules
- **High effort is the ceiling for a delegate.** xhigh and max buy a few points at 2–3× the
cost per task.
- **Reviewers run read-only.** A packet can carry injected instructions; only an implementer
gets write access. Codex delegates also skip your config and rules and turn apps off (see
SKILL.md for the flags and what they don't cover).
- **Caveats to put in every packet:**
- Codex models: "Do not remove or weaken any existing test." Some GPT models try
workarounds when access is denied, and Codex's sandbox has no network by default.
- Gemini: reads media and returns text. It runs in plan mode, so don't ask it to edit files
or run commands, and it doesn't generate images.
- **Handoff overhead** (writing the spec, reading the report and the diff) is real. Worth it for
another quota pool or for keeping the host's context clean; not worth it to move work to a
model that costs more per task.
## When two models disagree (council)
1. **Blind first.** The reviewer gets the artifact and what it must satisfy, never the host's
conclusion.
2. **Adversarial prompt:** "Find what is wrong. Don't validate. If nothing is wrong after a
thorough look, say so explicitly."
3. **Classify each finding:** the brief was unclear → real, fix it → real trade-off, the user
decides → noise.
4. **Tiebreak:** a benchmark lead settles it only if the question sits squarely in that
model's lead area **and** the gap is bigger than the error bar. Otherwise run a check on
the real task, or take it to the user.
5. **Three rounds at most**, then the user decides.
## Keeping this current
- **For users:** `git pull`. The watch (`model_watch.py`) tells you when a release lands before
this file catches up. With `AUTO_UPDATE_CLI=1` it also updates the CLI and proves the model
answers.
- **Release notes the watch reads:** the Codex changelog, OpenAI news, Anthropic's release
notes, the Claude Code changelog and Google's Gemini API changelog. Plan access is decided by
the vendor's own wording ("available in Codex and ChatGPT", "for Pro subscribers").
- **For the maintainer, on a new model (~15 min):**
1. Confirm plan access in the vendor's release notes.
2. Re-read the trackers below for every model in the table, not just the new one.
3. Bench it: `python3 bench/bench.py codex|claude|agy <model> [effort]`, then the current
holder of the route it would take. It takes the route only if it passes every task the
holder passed, at a higher score for no more cost per task (or within 1% for less). Results append to `bench/results.tsv`.
4. Redo the route table and "Why these picks". Bump the snapshot date.
5. For a new Opus, update `model:` in `agents/opus-implementer.md`.
6. Commit, then run `model_watch.py ack`.
**Trackers**, in order of trust: [Artificial Analysis](https://artificialanalysis.ai) (runs its
own evals, publishes cost per task) · [BenchLM](https://benchlm.ai) (per-field scores, shows
uncertainty) · [llm-stats](https://llm-stats.com). Vendor launch posts pick favourable benchmarks.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |