Hand routine coding from Opus to a cheap model that must pass its own test

A Redditor built Cheap Agent, a Claude Code MCP plugin where Opus plans and a half-cent DeepSeek model writes the code, cutting Opus tokens by 55 to 63% in their SWE-bench runs.

Done withClaude Code· Oct 30, 2026

What they did

The poster kept running out of their Opus allowance in Claude Code and saw that most of it went on mechanical work: reading files, writing boilerplate and rerunning tests. They built Cheap Agent, an MCP server and Claude Code plugin. Opus plans and writes a short task brief; DeepSeek V4.1 Flash, called through OpenRouter, does the edit in a separate git worktree. The cheap model has to add a test that fails before its change and passes after, and the plugin runs that test itself rather than trusting the model. Only passing work is applied, left uncommitted for a normal diff review. If the cheap model stalls, a Sonnet helper finishes the step. The poster had Opus design the tool and then used Cheap Agent to build the rest of it.

How it went

On SWE-bench Verified with Opus 5.5 and the same prompts, a feature task dropped from about 154k to 57k Opus tokens. Seven everyday bug fixes used 59% fewer Opus tokens and both setups solved all seven. On nine of the hardest bugs it saved 55% but solved six against Opus alone's seven. The Windows port was 30 delegated jobs costing $0.29 in DeepSeek calls. It gave no gain on tiny jobs, and an early demo saved only 20% because the repo had no test command, so Opus ran the tests itself.

Worth knowing

The savings depend on the repo having a working test command. The poster found that letting Opus decide what counts as simple failed, because it kept doing small edits itself; sending every code change to the cheap model worked better. Code goes to whichever provider you configure. Several commenters pointed out that subagents on a smaller Claude model do much the same, and one reported a long migration that a cheaper model kept failing until Opus took over.

Try it

With Claude Code· 3 parts to fill in

For this repo, act as the planner only. For every code change, write a short task brief and hand it to [my cheap model tool or a subagent on a cheaper model] instead of editing files yourself, even for one-line changes. Each brief must ask the worker to first add a test that fails without the change and passes with it. Run [the repo's test command] yourself after each handoff and accept the work only if that test and the existing suite pass. If the worker fails twice on the same step, take it over. Leave everything uncommitted and stop when [the feature or bug list] is done so I can review the diff.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related