Report · Cost vs quality · November 2026

Same result, half the price: a model “diet” for a coding agent

We gave the open-source coding agent Aider 27 programming exercises with hidden tests. We ran each exercise three times, changing only the model, and counted what each solved exercise cost.

ModelExercises solvedCost per solved exercise
Claude Opus 5.526 / 27$0.30
Claude Sonnet 5.526 / 27$0.15
Claude Haiku 5.522 / 27$0.009

Averages hide what you lose

A pass rate tells you how many tasks a cheaper model drops, not which ones. For each exercise that Haiku failed and the others passed, we re-ran the hidden tests on its final code:

Failing tests out of all tests for that exercise.

The main path usually worked. Edge cases and error handling were what broke. Whether that is acceptable depends on your work, so a cost decision needs the list of losses, not just the average.

How it was done

What this does not show

Doing this for your agent

If your agent's bill looks too high, the useful answer is not “use a cheaper model”. It is: here is a cheaper setup, here is proof that it does your tasks as well, and here is exactly what it gets wrong. We do this on 20–30 of your own tasks with known answers, and we fix your rare but critical cases before measuring.

The CSV has one row per exercise and model. The in_analysis column is 0 for the one exercise that finished for only one model.