<- all tokdocs

Claude Effort Levels: Does Max Effort Really Use 3x the Tokens?

By , founder of Mavric and Apso

View on TikTok ->

It does in one specific test. Anthropic's own benchmark sweep shows Claude Fable 5.1 using a median of 73k tokens per attempt at low effort and 222k at max effort on Terminal-Bench 3.0, about 3.04 times as many. A TikTok summarizing that result gets the number right but picks the wrong headline domain, and it applies coding results to business tasks the benchmark never tested.

The video, from @forgedlabsai (Forged Labs), opens with "Most companies are about to waste big money by asking AI to think deeply about everything." Its advice is to match AI effort to the cost of being wrong.

Where does the 3x token figure come from?

The chart in the video comes from Spending your effort, published on claude.dev on September 25, 2026 by Thariq Shihipar. The site describes itself as "technical writing for people building with Claude," sharing "POVs from Anthropic's developers." Shihipar's bio on ai.engineer lists him as a "member of technical staff at Anthropic working on Claude Code," so the video's "anthropic engineer" description is correct.

The article reports Claude Fable 5.1 at low effort as "370 attempts, median 73k tokens each" and at max effort as "370 attempts, median 222k tokens each." That ratio is 3.04. The 370 attempts match the benchmark: Terminal-Bench 3.0 shipped in July 2026 with 74 tasks, and 74 tasks at five attempts each is 370.

The video leaves out the scope. The figure covers one model, Claude Fable 5.1, at the two ends of a five-level scale (low and max), on one benchmark. The chart plots four models with four separate curves, and the narration names none of them.

Which tasks benefit most from higher effort?

The video says higher effort helped "especially security." The article's domain table shows pass rates at low and max effort:

Domain Low Max Change
Security 64% 87% +23 points
Hardware 34% 75% +41 points
ML 54% 73% +19 points
Science 41% 61% +20 points
Software 43% 56% +13 points
Media 18% 30% +12 points
Operations 12% 22% +10 points

Security improved, but hardware gained the most, at 41 points against security's 23. Hardware more than doubled its pass rate.

The security framing does hold for one example in the article. A task called html-js-filter asks for "an HTML sanitizer that strips every way of smuggling JavaScript into a page," and "Fable 5.1 went from 1/5 at low to 5/5 at xhigh." That is one task, not a domain ranking.

Does higher effort help less on routine tasks?

The video says higher effort "delivered much smaller gains on some routine tasks." In percentage points, operations (+10) and media (+12) had the smallest gains, so the claim holds on that measure.

Two details complicate it. The article never calls those domains routine. They are the two where the models score worst overall, and operations reaches only 22% even at max effort. In relative terms, operations rose from 12% to 22%, an 83% increase, and media from 18% to 30%, a 67% increase. Both are larger relative gains than security's move from 64% to 87%.

How Anthropic suggests choosing an effort level

The article's guidance is written for coding:

  • Low: "for when I want quick responses that are in the loop, e.g. brainstorming, sketching, easy changes."
  • Medium: "for most of my regular software engineering work, e.g. new feature implementation."
  • High: "for work where verification is important or there are edge cases, e.g. fixing a bug in a brownfield codebase."
  • Max: "When I want Claude to operate fully autonomously to solve difficult problems, e.g. end to end building and verification of an app."

Does this apply to finance and compliance work?

The video extends the advice to "financial analysis," "customer commitments," "compliance and final verification." None of those are in the source.

Terminal-Bench describes itself as "a benchmark to measure and evolve with the frontier of agent work," hosted by Stanford, Harbor and the Laude Institute. Snorkel AI describes it as testing whether agents can operate real terminals, "writing and debugging code, configuring environments, and recovering from failure, all without a GUI." The article's domains are hardware, science, ML, software, security, operations and media. There is no finance, compliance or customer-commitment task.

The extension to business work may be a reasonable analogy, but it is not a finding from this data. The opening claim about companies wasting "big money" comes with no spend figure or source.

Is a cheaper model a better lever than effort?

The chart carries an annotation the narration never mentions: "same score, half the tokens." It sits beside the Opus 5.5 "high" point, level with the Fable 5.1 "max" point at about twice the token count. The article says "Fable 5.1 and Opus 5.5's effort curves are our best yet: at each level, there is an uptick in benchmark scores and tokens consumed."

Pricing widens the gap. Per Anthropic's pricing page:

Model Input per MTok Output per MTok
Claude Opus 5.5 $4 $20
Claude Opus 5 $5 $25
Claude Fable 5.1 $10 $50
Claude Fable 5 $10 $50

Opus 5.5 costs 40% of Fable 5.1 per token. Anthropic's Opus 5.5 launch page says "Opus 5.5 at default effort beats Opus 5 at max effort for about a fifth of the cost." Following only the video's advice means adjusting effort while leaving model choice alone, and on this chart model choice is the bigger lever.

The pricing page also notes that Claude 4.7 and later models use a tokenizer that "produces approximately 30% more tokens for the same text." Every model on the chart is post-4.7, so the comparisons between them are consistent.

Bottom line

The 3x figure is accurate for Claude Fable 5.1 going from low to max effort on Terminal-Bench 3.0. Hardware, not security, gained the most from higher effort. The benchmark covers terminal coding tasks only, so applying it to finance or compliance is an analogy. Switching from Fable 5.1 to Opus 5.5 can cut cost more than lowering effort.

Sources

Published October 5, 2026. Based on a TikTok by @forgedlabsai. Full video notes (markdown)