Opus 5.5 matches Fable 5.1 for 60% less: is Fable still worth using?
Back to the blog
Articlemodelos de IAbenchmarksagente de programaçãoverboo code

Opus 5.5 matches Fable 5.1 for 60% less: is Fable still worth using?

MafraSeptember 25, 20265 min read

Three days after launch, the most repeated question on r/ClaudeAI is blunt: "if Opus 5.5 is basically Fable level, what are you still using Fable for?" (September 25, 2026). Anthropic's numbers side with the people who switched everything. Artificial Analysis's numbers show where that math misleads.

What did Anthropic release on September 22?

Claude Opus 5.5 (claude-opus-5-5), at US$4 per million input tokens and US$20 per million output tokens, 20% below Opus 5. Fable 5.1 costs US$10 and US$50, which is 2.5 times more per token. The official line is that Opus 5.5 "performs at the level of Claude Fable 5.1 on most work", and that in Anthropic's own use the gap between the two is narrower than the benchmarks suggest.

Opus 5.5 or Fable 5.1: which one wins on benchmarks?

Opus 5.5 wins most of the coding agent benchmarks Anthropic published. Fable 5.1 still leads some independent reasoning and long-context tests.

CriterionOpus 5.5Fable 5.1Source
Price (input / output, per 1M tokens)US$4 / US$20US$10 / US$50Anthropic, VentureBeat
Terminal-Bench 4.066.4%55.8%Anthropic
CursorBench 4.057.8%51.8%Anthropic
FrontierCode v1.154.4%50.3%Anthropic
OSWorld 2.081.8%80.7%Anthropic
Output tokens per task (max effort)~119k~78kArtificial Analysis
CritPt, AA-LCR, GDP.pdfbehindaheadArtificial Analysis

Sources: Anthropic's announcement, VentureBeat and Artificial Analysis, all from September 22, 2026. Terminal-Bench, CursorBench, FrontierCode and OSWorld scores are self-reported by Anthropic.

What is the case for switching everything to Opus 5.5?

Price and scoreboard. Opus 5.5 beat Fable 5.1 on Terminal-Bench by more than 10 points, costs 60% less per token and, according to Artificial Analysis, took the top spot on the Intelligence Index with a score of 58 at max effort. In the thread, a user on the 20x plan reports that for the first time they used less Fable than Opus in a week and had quota left over. The thread's automatic summary calls Opus 5.5 the new default model for 80 to 90% of tasks.

What is the case for keeping Fable?

Hard tasks and review. One of the most upvoted comments in the same thread, and several others, describe Fable as an escalation model: planning a feature with many dependencies, a bug spread across several files, reviewing the plan Opus wrote. Independent data backs part of this: Artificial Analysis shows Fable 5.1 still ahead on CritPt (scientific reasoning) and AA-LCR (long-context reasoning).

And there is a detail almost nobody runs the numbers on: at max effort, Opus 5.5 spends about 119k output tokens per task, versus 78k for Fable 5.1 and 73k for Opus 5. That is 1.6 times the tokens of its predecessor.

So how much does Opus 5.5 really save per task?

Much less than the 60% per-token price cut. Output only, at max effort, using the numbers above:

Opus 5.5:  119,000 tokens x US$20 / 1M = US$2.38 per task
Fable 5.1:  78,000 tokens x US$50 / 1M = US$3.90 per task
Real difference: ~39% cheaper, not 60%

Artificial Analysis reached the same conclusion another way: with input and cache included, Opus 5.5 at max costs US$5.98 per index task, practically the same as Opus 5 (US$5.86). The price cut was almost entirely eaten by the token increase. It is still cheaper than Fable, but the savings come from the price sheet, not from spending less.

Where does Verboo Code stand on this?

Both sides are right, and the thread reached the answer on its own: a default model for volume and an escalation model for the hard case. The mistake is treating the choice as permanent. The useful question is not "which one is better", it is "which one solves this task at the lowest cost per solved task".

In Verboo Code this pattern already lives in the terminal. You switch models mid-session without losing history:

/model              # opens the list of models unlocked on your plan
/model <id>         # switches directly, session context stays
/effort max         # raises reasoning effort just for the hard task
/effort auto        # goes back to the model default

Or leave the choice to the router: the jev-router alias picks the model on every request, and since v0.15.31 the CLI shows which physical model answered (for example jev-router → glm-5.3-flash). More in how to switch models without losing context and in dynamic model routing in Verboo Code.

The number that weighs most in this debate is 119k tokens per task: a model that thinks more costs more, even when the price per token drops. On Verboo Code plans run with unlimited tokens, so raising effort for the hard task changes how fast the answer comes, not your bill.

Enjoyed this article?
Share knowledge with your network.
// Read also

Related articles