TechniquecurrentRunning agents

Use the top model to plan and review, and cheaper models to write

My top model writes specs and reviews, while cheaper models do the typing.

SymptomA top-model session hits its context or usage limit after a few prompts spent reading raw tool output.

The most capable model is the one I run out of first. In an interactive session it also carries the most fixed overhead, because it re-reads the instructions, tool schemas and the whole conversation every turn.

So my top-tier session only plans, writes specs, dispatches, reviews and integrates. The bulk runs in disposable contexts on cheaper models:

  • A pinned-Opus builder drafts against a written spec.
  • A research agent does the sourcing.
  • A Haiku checker runs pass/fail checks with read-only tools.

The spec keeps the cheaper model safe. It carries locked decisions, the files to read, the deliverables and a return contract. The builder flags any deviation instead of redesigning.

A vague spec moves the design work onto the cheaper model.

As the Claude Code subagent documentation lays out, sub-agents inherit the session's model unless the call, the agent's own definition or the CLAUDE_CODE_SUBAGENT_MODEL variable sets one. With none of them set, the saving disappears with no error.

On an early build of a scoring rubric done this way, the draft needed two small integration fixes, and more than 200k tokens of drafting, research and testing stayed off the top model.

Check your setup read-only

Take the 3 longest of your last 10 top-model sessions by turn count. Count the tool calls that returned raw data in each transcript. Count the calls that returned a sub-agent's conclusion. If raw-data calls outnumber conclusions, the top model is doing the work instead of planning it.

Passes ifIn each sampled session's transcript, calls that returned conclusions equal or outnumber calls that returned raw data.

Access needed:agent-transcripts

If it fails: changes to make later (not part of the check)
  1. 01Keep the top model on intent, specs, review and integration.
  2. 02Write the spec before dispatching, including locked decisions, files to read, deliverables and a return contract.
  3. 03Set a default sub-agent model in config with the CLAUDE_CODE_SUBAGENT_MODEL variable. Pass a model explicitly where it differs from the default. Do not let a sub-agent inherit the top model.
  4. 04Send an investigation to a sub-agent when the raw output would cost more than the sub-agent's start-up cost. Have the sub-agent return conclusions, not raw output.
  5. 05Keep work of 2 tool calls or fewer, single-file edits and judgment-dense integration in the main session.
Applies ifYour top-model session transcripts list a tool that spawns sub-agents, and some sessions reach their context or usage limit.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.