Claude Opus 5 Is Here — and Half the Instructions in Your Setup Just Expired

Anthropic shipped Claude Opus 5 today. The headline number is the one you would expect: near-frontier quality at half the price of the frontier. It comes close to Fable 5 on the benchmarks Anthropic publishes, at $5 per million input tokens and $25 per million output — the same price as Opus 4.8, and half of Fable’s $10 and $50. On CursorBench 3.2 it lands within half a percent of Fable’s peak score at half the cost per task. It is now the default on Max and the strongest model on Pro, with a one-million-token context window as both the default and the ceiling.

So the question everyone is asking today is should I switch.

That is the wrong question, and it is the wrong question in an interesting way. A model launch does not hand you a new option and leave everything else intact. It invalidates the compensations you built for the old one. Two separate things in my setup went stale this morning, and neither of them is a model name in a config file.

The first thing that expired: my routing table

When Fable landed in June, I argued the disciplined move was to route down, not up — that a new top tier makes the routing decision more consequential, not the frontier more attractive. I drew a line between advanced work (strong reasoning on an established pattern) and frontier work (genuine invention, no pattern to follow), and reserved the expensive tier for the second.

That line was drawn against a specific price. Frontier cost $10 and $50. Advanced cost $5 and $25. The gap between them was wide enough that “is this genuinely invention?” was a question worth asking carefully, because getting it wrong cost double.

This morning the gap closed from the bottom. Near-frontier results now come out of the Opus lane at Opus prices. The frontier did not move up — the price of almost-frontier moved down.

The consequence is the opposite of the reflex. It is not “the good stuff is cheaper, so use more of it.” It is that the slice of work which genuinely justifies the top tier just got narrower, because the tier below it now covers more ground for the same money it always cost. My advanced-versus-frontier boundary was calibrated against a price ratio that no longer exists, and a boundary calibrated against stale numbers is not a discipline. It is a habit.

The tiering decision did not get easier. It got re-drawn without my involvement.

The second thing that expired: my instructions

This is the part that will not make the launch coverage, and it is the more expensive of the two.

Anthropic published a prompting guide for Opus 5 alongside the model, and a striking amount of it is a list of things to take out of your prompts:

• Remove explicit verification instructions — a final verification step, a subagent to check the work. The model already verifies itself, so these “cause over-verification,” and deleting them cuts wasted tokens with no loss in quality.
• Remove instructions to double-check or re-verify before answering. Same mechanism: the behavior is already there, and the instruction compounds with it.
• Stop telling a code-review prompt to be conservative or to report only high-severity issues. Opus 5 follows that literally and reports less. Ask for everything and filter in a second pass.
• Cap subagent delegation. The model reaches for subagents more readily than its predecessors, which is expensive when the task did not need parallelism.
• Re-run your effort sweep. Settings you tuned on a previous model no longer describe the same quality-per-token curve.

Read that list again and notice what every item has in common. Each one is a compensation for a weakness that no longer exists. Nobody wrote “double-check your answer” as a stylistic preference. They wrote it because a model once shipped an answer that did not survive contact with a second look. The instruction was earned. It was a fix for a real failure, and it worked.

And then it stopped being a fix and became furniture.

Why these are one problem, not two

A stale routing table and a stale prompt look like different maintenance jobs. They are the same one: configuration written against a model that no longer exists.

What makes this failure class durable is that the stale parts feel like rigor. Deleting a routing rule feels like cutting corners. Deleting “verify your work before responding” feels like removing a safety net — and safety nets are not the thing you delete on launch day, when everything else is in motion.

But rigor and workaround are not the same substance, and they do not age the same way. Genuine rigor is indefinite. A workaround has an expiry date set by the thing it was working around. When the weakness is gone, the compensation does not become neutral — it becomes a tax. Over-verification costs tokens and latency. A “be conservative” instruction now costs you real bugs the model found and then declined to mention. That one is worth sitting with: the instruction you added to reduce noise is, on this model, an instruction to withhold findings. It is gate erosion arriving through the front door, in a line you wrote yourself, months ago, for a good reason.

The distinction worth keeping

There is a version of this advice that would be wrong, so let me draw the line precisely, because I am not throwing out verification.

Verification that consults an external source of truth stays. Run the test and read the output. Check the file exists before claiming it does not. Read git status before describing the working tree. That is not the model double-checking itself — that is the model acquiring evidence it did not previously have. No model improvement makes that redundant, because the information lives outside the model. My own operating rules are thick with this kind of check, and none of it is on the chopping block.

Verification that asks the model to re-examine its own output goes. “Review your answer.” “Are you sure?” “Add a verification step at the end.” That is redundancy, not evidence — a second pass over the same information, hoping for a different result. It was worth paying for when the first pass was unreliable. Anthropic is now telling you, in writing, that on this model you are paying for it twice.

Evidence, keep. Self-doubt, delete. Most prompt scaffolding that survived from 2025 is the second kind wearing the costume of the first.

The audit, which takes an afternoon

If you build with AI, this is a grep. Search your prompts, skills, system messages, and agent harnesses for the compensation vocabulary — double-check, verify before, re-read, be conservative, only report, make sure to confirm — and for each hit ask one question: is this instruction fetching new evidence, or asking for a second opinion from the same source? Delete the second kind. Then re-run your effort sweep, because your defaults were tuned on a different curve.

If you run a business on AI rather than building it, you do the same audit in a different place: the standing instructions in your custom GPTs, your assistant setups, the preamble you paste at the top of every long task. Same question, same answer.

Either way, budget an afternoon, and do it before you touch a single model name. Swapping the model is the five-minute part. Removing the scaffolding you built around its predecessor is the work — and it is the part that determines whether the upgrade shows up in your bill as a saving or an increase.

That is the whole difference between marketing-grade and engineering-grade practice on a launch day. Marketing-grade asks which model to switch to. Engineering-grade asks what in the system just became wrong — and then goes and deletes it. If you build, that audit lives in your tooling: the software-engineer track. If you operate, it lives in how you run the business: the solopreneur track.

A launch is a maintenance event

Opus 5 is genuinely good news, and the price-per-capability move is the most consequential thing in it — more than any benchmark. Anthropic also reports it is the most aligned model they have audited, with the lowest rates of deceptive behavior they have measured. Take the win.

But the win is not automatic, and it is not collected by switching. Every model launch quietly deprecates a layer of your setup, and that layer never announces itself, because it looks exactly like the care you took last year. It was the care you took last year.

The model got better. Your instructions didn’t. Go delete some.