Claude Fable 5.1 launches with benchmark lead and cost controversy

Anthropic's headline is a 75% cut to cache-read pricing, from $1.00 to $0.25 per million tokens, which the company says lowers typical workload costs by about 25% and highly agentic workload costs by up to 45% ^[4]. That framing survives contact with Artificial Analysis's own testing only partway. The benchmarking firm found that at maximum reasoning effort, Fable 5.1 actually costs about 20% more per task than Fable 5 - $3.76 versus a lower baseline, and without the cache-read cut it would have run closer to $5.16 ^[6]. The reason is that Fable 5.1 burns through roughly 1.7x more output tokens per task at max effort, and output tokens are still billed at the unchanged $50-per-million rate, so the savings on cached reads get eaten by the extra generation. Compared with Opus 5 at max effort ($2.34 per task), Fable 5.1 runs about 61% more expensive for its top score. The-decoder.com's read is blunt: the cache cut genuinely saves close to $1.40 per task on agentic workloads, but that saving is real only if you don't also crank the effort dial up ^[7]. Independent LLM evaluator Simon Willison captured the same tension anecdotally on X, noting that Max thinking level produced his best-ever SVG pelican output from an Anthropic model, at what he called 'a hefty cost of $3.30' for a single test.

Fable 5.1 and Mythos 5.1 are not two different models - independent reporting describes them as the same underlying system, differentiated purely by which safeguards are switched on ^[2]. Mythos applies safeguards tuned for cybersecurity and life-sciences work and is restricted to a vetted, invitation-only set of US organizations ^[1]. Alongside the launch, Anthropic introduced Enterprise Frontier Safeguards (EFS), a privacy architecture that lets customers store misuse-monitoring data on their own cloud infrastructure while Anthropic's detection systems still operate against it - explicitly pitched as combining the privacy of a zero-data-retention agreement with active misuse detection ^[1]. The safeguard tuning appears to be working in the direction Anthropic wants: roughly 60% fewer cybersecurity false positives and about 85% fewer refusals on benign biology and medical questions compared with Fable 5 ^[4]. But the improvements haven't eliminated friction in practice. On Reddit, professional users in regulated fields such as biotech, nursing, and pharmacokinetics reported being automatically downgraded to Opus 5 mid-task, and one widely watched build-log video described an automatic safety-flag downgrade triggered mid-project during a cybersecurity-adjacent operation - suggesting the new safeguard tuning still catches legitimate professional work in its net.

The raw score movement is unusually large for a point release. Terminal-Bench-Science 0.1 more than doubled, from 24.7% for Fable 5 to 52.6% for Fable 5.1, and Terminal-Bench 4.0 climbed from 42.0% to 55.8% (Mythos 5.1 reaches 60.9%) ^[7]. AutomationBench nearly doubled too, from 17.1% to 31.4% ^[3]. Those gains land Fable 5.1 at the top of Artificial Analysis's Intelligence Index at 66, ahead of the Opus 5 model Anthropic released only weeks earlier at 63, and ahead of GPT-5.6 Sol and Grok 4.6, both at 61 ^[6]. The competitive positioning matters given the launch's timing: Fable 5 spent part of June offline after a US export-control directive, only returning globally with updated safeguards on July 1 ^[8], and Opus 5 arrived less than six weeks before Fable 5.1 ^[6]. Coming so soon after Opus 5, Fable 5.1's benchmark lead reads less like an incremental patch and more like Anthropic trying to reclaim the top of the leaderboard before rivals catch up - a read reinforced by one French-language launch-day demo that built a full CRM application from a PRD (product requirements document) in about 80 minutes, citing the same agentic-coding and knowledge-work benchmark figures straight off Anthropic's own announcement.

The clearest real-world evidence for the marketing-versus-measured-cost gap isn't in a benchmark report - it's in how fast early users are burning through usage allowances. One widely discussed Reddit build, where a single prompt led Fable 5.1 to spin up roughly 14 parallel subagents to construct a browser game, consumed nearly 2 million output tokens and over 118 million cache-read tokens, exhausting the poster's five-hour usage limit in about an hour. A separate X post described blowing through 28 Max 20x plan allocations in a single day, which the poster attributed to a possible caching bug. Two of the Reddit threads independently raised the same complaint: rapid five-hour usage-limit exhaustion, alongside some skepticism in the comments that flashy multi-agent showcase posts might be astroturfed. Taken together with Artificial Analysis's finding that Fable 5.1 uses about 1.7x more output tokens at max effort, this pattern isn't really a separate story from the pricing controversy - it's the pricing controversy showing up in practice. Highly agentic, multi-subagent orchestration is exactly the workload style that multiplies output-token volume fastest, which is also where the headline 45% savings claim is most likely to invert into a real cost increase.