Anthropic just shipped Claude Fable 5, and it is, by its own benchmarks, the most capable model the company has ever made publicly available. It’s the safety-constrained public form of a new tier they call Mythos-class — a rung that sits above Opus. It’s built for long-running agents: days-long autonomous sessions, large migrations, frontier reasoning, vision.
The reflex, the moment a more powerful model lands, is obvious: route everything to it.
That reflex is exactly how you burn money and trust.
A new top tier doesn’t mean “route up.” It means “route carefully.”
Here’s the thing a model launch never tells you: most of your work doesn’t need the most powerful model. It never did.
Extracting fields from a transcript is mechanical. Drafting a customer reply, or writing a unit test against an established pattern, is execution. Summarizing a long report — or a year of your own notes — is a big job, not a hard one. None of that got more difficult the day Fable shipped — and none of it gets better on a frontier model. It just gets more expensive, and you don’t see the waste, because over-spending on intelligence is invisible. A model that’s quietly too weak gives you a wrong answer you can catch. A model that’s needlessly too strong gives you the right answer and a bill you never inspect.
So a new tier above Opus doesn’t move my work up the ladder. It makes the routing decision one notch more consequential — because now there are four tiers to get right instead of three, and the most expensive one is genuinely expensive.
The skill was never “use the best model.” The skill is: route every task to the cheapest model that can do it reliably — and no cheaper.
What actually decides the tier
Three distinctions do almost all the work, and none of them is “how important does this feel.”
Execution versus judgment. Plenty of important work is execution — the tests for a critical payment module follow an established pattern, and so does sorting a week of support tickets into known buckets. Both are mid-tier work, not frontier work. Plenty of routine-sounding work is judgment — a one-line pricing change, or a single sentence in a contract, can lock in a year of revenue. Whether you’re shipping code or running a business, route on what the task demands, not on who’s asking or how it’s labeled.
Advanced versus frontier. This is the new line Fable draws. Strong reasoning on an established pattern — designing a service, reviewing security-critical code, setting next quarter’s pricing — is advanced work; Opus handles it. Invention — designing a whole platform with no pattern to follow, or building a business model that has no template — is frontier work. That’s the narrow slice Fable earns. The tell: is there a pattern an expert would follow, or does one have to be invented? Most “hard” work has a pattern.
Size and duration are not difficulty. A large corpus is a context problem, not a reasoning one — summarizing a whole repository is still a cheap-model job, it just needs a big window. A multi-day migration is a harness problem — the work spans many sessions, but each step is ordinary; the scaffolding carries the duration, not the model. Neither one is a reason to escalate to the frontier. Reaching for Fable because a job is big or long buys you nothing the window or the harness wasn’t already going to provide.
Get those three right and the frontier tier becomes what it should be: rare.
What I did the day it shipped
I rebuilt my routing.
I keep a small skill — a model-router — whose entire job is to look at a task and emit one decision: Haiku, Sonnet, Opus, or now Fable. One token, nothing else. Fable’s arrival meant adding the frontier tier and tightening the line above Opus so that “important,” “large,” and “long-running” stop leaking work upward into the expensive lane.
And I split out a second skill — a work-router — because I’d been conflating two different decisions. Which model a task needs is one question. How to run the work — whether to break it into a pipeline, stand up a long-running harness, fan out parallel sub-agents, hold a large context — is a completely separate one, and it usually matters more. (Anthropic’s own engineering guidance is blunt about this: even a frontier model “will fall short if it’s only given a high-level prompt.” The harness and the decomposition often decide the outcome more than the tier does.) So now one skill routes the work and hands the model question to the other. Two skills, one responsibility each.
You may never write a router skill — and you don’t have to. But you make the same decision every time you pick a model for a task, or let a tool pick one for you. The discipline is identical whether you codify it in a skill or hold it in your head: the cheapest model that does the job reliably, with the frontier reserved for genuine invention. A builder writes it down once; an operator makes the call in the moment. Same call.
I’m dogfooding both skills in my own setup right now, with the intent to fold them into the foundation pack that ships with my courses once they’ve earned it on my own work. That’s the rule I hold myself to: nothing ships to students until it’s survived contact with my real pipeline first. If you build with AI, the routing lives in your tooling — that’s the software-engineer track. If you run a business on AI, it lives in how you operate — that’s the solopreneur track.
The boring lesson the launch won’t sell you
A more powerful model is genuinely good news. Fable will do things this week that nothing could do last week, and the frontier slice it owns is real.
But the durable advantage was never the model you reach for. It’s the discipline that decides when to reach. Marketing-grade work chases whatever shipped this morning. Engineering-grade work builds the routing once and lets it compound — cheaper, more reliable, quietly correct — across every model launch that follows. Fable is the fourth tier I’ve routed to. It will not be the last. The routing is the part that lasts.
The frontier moved up. The discipline is to route down.