Claude Opus 5 Beats Fable 5 on Benchmarks at Half

There's a specific kind of chaos that descends on developer communities when an AI release lands and scrambles everyone's priors. Claude Opus 5 is that release.

Anthropic shipped Claude Opus 5 with a benchmark sheet that should not, on paper, be possible: a model positioned below their flagship Claude Fable 5 in the model family hierarchy, priced at $5 per million input tokens and $25 per million output tokens — the same price as Opus 4.8, and half the price of Fable 5 — outperforming Fable 5 on most of the benchmarks that practitioners actually care about. Reviewer Matthew Berman, who got early access, put it plainly: "Is Opus beating Fable 5 on almost every benchmark?" His answer, working through the data: yes, essentially.

The numbers that caught the most attention: a jump from 33 to 43 on Frontier Bench (a coding benchmark developers treat as a reliable signal), a 100-point improvement on GDPVal (OpenAI's real-world practical tasks benchmark), a four-point gain on OS World (computer use), and a nine-point improvement on Automation Bench. On ARC AGI 3 — more on that in a moment — Opus 5 hit 30%, against a previous best of around 8% from any model.

Not everything moved up. The legal benchmark dropped from 13.3 to 11.7. HealthBench Professional also declined. DeepSui, which Berman considers the most vibes-predictive benchmark ("if I were to point to any benchmark and say this is probably the vibes you all and myself are going to feel, this is it"), showed a slight drop — essentially flat. The pattern, if you squint at the full picture, is a model that trades away some domain-specific depth for broad agentic and reasoning capability. Whether that trade is worth it depends entirely on what you're building.

The ARC AGI 3 Number Deserves Its Own Paragraph

ARC AGI 3 is a benchmark that deliberately withholds context. The model is dropped into a game with no instructions, no name, no explanation — just the task itself and a finite number of moves. Humans can solve these. Prior to Opus 5, the best any model had managed was roughly 8%. Opus 5 hit 30%.

That's not an incremental improvement. That's a discontinuity. Whether it reflects something genuinely different about Opus 5's reasoning architecture, or whether it reflects how Anthropic has been training against this specific benchmark, is a legitimate open question. But the number is hard to wave away.

Cost Per Task Is the Actual Argument Here

The benchmark scores are attention-grabbing, but Anthropic's real pitch with Opus 5 is a reframe of how you should think about model economics. The relevant unit is not price per token — it's cost per task.

Berman has been making this argument for weeks, and Anthropic appears to have built it directly into how they're presenting Opus 5's value. The OS World cost-per-task chart in the release materials tells the story visually: Opus 5 sits higher (better performance) and further left (lower cost) than both Fable 5 and Opus 4.8 on computer-use tasks. GPT 5.6 Soul, by comparison, has a wide spread of cost depending on configuration — and even at its lowest, according to Berman's reading of the chart, costs more than twice as much to match Opus 5's performance.

The Kimi K3 comparison is instructive here. A model can be half the token price and still cost the same to accomplish a task if it burns twice the tokens to get there. Berman: "It is the main metric you need to be looking at is cost per task. That is it." This is increasingly the frame developers are adopting when evaluating model efficiency, and Anthropic appears to be meeting them there deliberately.

What the Enterprise Data Shows

Box, which sponsored Berman's video, ran Opus 5 against Opus 4.8 on what Box's own benchmark materials describe as realistic document-grounded tasks across twelve industries — reading source documents, reconciling numbers, running due diligence, reviewing expert output. The Box blog has separately covered enterprise AI performance comparisons in this space.

The results, as presented in the sponsored segment: legal review jumped from 63 to 78, due diligence from 65 to 76, data analysis up six points. Report drafting and expert review were roughly flat. The framing from Box: "Claude Opus 5 is a clear step up from the prior generation. Its advantage concentrated on the exhaustive multi-step analysis that drives real decisions."

Worth noting that this is sponsored benchmark data, presented by a commercial partner with an interest in the result. The directional signal is consistent with Anthropic's own numbers, but the enterprise framing reflects Box's evaluation priorities, not an independent audit.

The Cybersecurity Carve-Out Is Deliberate

One place Opus 5 explicitly trails: cybersecurity exploit development. Berman notes that Opus 5's exploit success rate sits at 4, versus 13 for Mythos 5, which appears to operate without comparable guardrails. Opus 4.8 was at zero.

The interpretation Berman offers — flagged as speculation — is that Anthropic actively trained capability out of this domain. What makes the Opus 5 story unusual is that this reduction in a specific capability area appears not to have dragged down overall performance, which is typically what happens when you constrain a model. Berman: "Typically, when you remove capabilities from a model, you hurt the model generally, right? It performs worse generally. But we're actually seeing the opposite effect here."

That's either a genuine alignment research win — demonstrating that targeted capability removal doesn't require broad performance sacrifice — or it's a measurement artifact, and the benchmarks just don't capture where the constraints bite. The community will stress-test this in the coming days.

The Fallback Question

Opus 5 ships with automatic safety classifier fallbacks — if a request triggers the classifier, the API can route it to a fallback model. Users pay the fallback model's price. Berman finds this annoying; others will find it acceptable. The more interesting signal is from r/ClaudeAI on Reddit, where the Opus 5 Incoming thread already has developers reporting Opus 5 falling back to Opus 4.8 due to safety filters. The classifiers may be more permissive than Fable's, but the architecture is the same — and for developers building production applications, unexpected fallbacks mid-task are a real reliability concern, not just an aesthetic complaint.

The developer reception, more broadly, has the quality of cautious enthusiasm. The pricing is genuinely competitive. The benchmark performance is hard to argue with on its face. The questions cluster around the same places they always do with Anthropic releases: how aggressive are the safety classifiers in practice, how does performance hold up in production workloads that don't look like benchmarks, and what does "rounds out our Claude 5 family beautifully" mean for the roadmap — specifically whether a Haiku 5 is still coming at the accessible end of the tier.

Anthropic's Turk wrote that Opus 5 is "an incredible daily driver" — suggesting it as a pairing with Fable for the hardest problems, which is an interesting positioning move. It acknowledges Fable retains relevance for ceiling-level tasks while conceding that Opus 5 covers most of what most people need, at half the price. That's a defensible product strategy. It's also an implicit admission that Fable 5's value proposition at its price point just got significantly harder to justify.

The broader context: the Sonnet 5 vs. Opus 4.8 comparison already showed Anthropic aggressively compressing performance down into lower tiers. Opus 5 continues that pattern upward — taking what Fable established and delivering it at a price that makes Fable harder to recommend for anything but the most demanding tasks.

Three models now sit at what Berman calls the "Pareto frontier" of cost and quality: Opus 5, GPT 5.6 Soul, and Kimi K3 (open-source). That's the actual competitive landscape developers are navigating. The question isn't whether Opus 5 is good — the benchmarks suggest it is. The question is whether the safety classifier behavior in production matches what the launch materials imply. That answer will come from the community in the next week or two, not from a benchmark sheet.

Dev Kapoor covers open source software and developer communities for Buzzrag.