- Genial
- Tutorial su IA e automazione
- Claude Fable 5 Is Here to Stay - Maximize Your Usage
Claude Fable 5 Is Here to Stay - Maximize Your Usage
Fable 5 is now here to stay as part of the Max 5X and 20X plans from Anthropic, but your real budget for it is much smaller than it looks. In this walkthrough I show you the setup that fixes that: turn Fable 5 into your orchestrator and verifier while Opus 4.8 subagents do all the busy work, configured once in a CLAUDE.md file.
What you need
- An Anthropic Max plan (5X or 20X)
- Claude Cowork or Claude Code; I demo in Cowork, but the steps are literally the same in Claude Code
- A project folder to work in; I recommend one single personal workspace folder you always stay in
1. Why your Fable 5 budget is smaller than it looks (0:12)
Fable 5 is staying, but you only get fifty percent of your weekly usage allowance for it. That means your 20X and 5X plans are essentially 10X and 2.5X. On top of that, Fable 5 consumes credits twice as fast as Opus 4.8, so cut in half again: you are getting a quarter of the extra usage you would normally get with a model like Sonnet 5 or Opus 4.8. If you use Fable 5 for literally everything, from replying to emails to creating your applications, you are not going to make it to the end of the month on either the one hundred or two hundred dollar plan.
2. Use Fable 5 as a delegator, not for busy work (0:52)
The conclusion is simple: to get the best bang for our buck, we do not use Fable 5 for busy work, we use it as a delegator. Fable 5 becomes the planifier and the verifier, while Opus 4.8, the model you get one hundred percent of the usage of, does all the busy work: reading text, writing, fixing, whatever you need. This setup will last you weeks. It is what I use personally, and it was very hard for me to reach the weekly limits with it.
3. Setting up in Claude Cowork (2:31)
Anthropic's own notice confirms the fifty percent weekly limit, so let's set up the fix. In Claude Cowork, open the project you are going to work in; I open a new test project for the demo. First, check whether the project already has instructions:
Hey Claude, is there a particular CLAUDE.md file inside of this workspace and this folder where we're working on?
The CLAUDE.md file is pretty much just the extra instructions you give to Claude, and you can be very specific: point it at your CRM, your folders, your content management services, anything. Since my project is new, there is no CLAUDE.md file yet.
4. The orchestrator and verifier instructions (3:33)
Now we create the file with the mode of operation that makes the whole thing work:
I want to create a new CLAUDE.md file. What's going to be super important is I want you to add the following mode of operation. Whenever I give you very complex tasks or very long tasks, I want you to break them up into sub-tasks, and then you will delegate those to your Opus 4.8 subagents. That's extremely crucial: not Fable 5 subagents, but Opus 4.8 subagents. On top of that, you will work as the orchestrator and also the verifier. So you will orchestrate all of those subagents, and then you will verify that what they did was actually correct. The idea is we want to maximize Fable 5 usage.
A note on the chat application: you cannot do this efficiently there, because giving custom instructions like this is quite hard unless you dig into the Settings tab. Switch to Cowork or Claude Code anyway.
5. Reviewing the new CLAUDE.md file (4:43)
I cut the video while it wrote, and came back to a brand-new CLAUDE.md implementing the orchestrator and verifier mode: it decomposes everything it does, breaks work into Opus subagents, orchestrates them, and verifies the results. If you know how you work, explain that to Claude Cowork too, so it writes a CLAUDE.md that is customized for you.
6. Testing with 3 Opus 4.8 subagents (5:10)
Time to prove the setup works:
Can you run a quick test for me? I want you to conduct research on the latest AI news in France, Spain, and Germany using three different subagents so that we see that all of this is working correctly.
Cowork starts creating subagents with its tools, and all three show up running on Opus. That is the whole point: we get the usage we are actually paying for instead of one quarter of it. The same applies whether you are developing applications or just pushing through busy work.
7. Recap: the highest-leverage setup (6:10)
Using Fable 5 purely as an orchestrator and delegator saves you so many credits it is not even funny. Fable 5 costs one hundred to two hundred dollars a month to access, but it remains the best model out there for delegation and creative work, and this configuration is the highest leverage you can get out of that subscription.
Pitfalls and tips
- Do the math before you burn the budget: fifty percent allowance times double credit consumption means a quarter of the usage you expect.
- Be explicit that subagents run on Opus 4.8, not Fable 5, or the delegation saves you nothing.
- Skip the chat application for this; custom operating instructions belong in a CLAUDE.md inside Cowork or Claude Code.
Where to go next
- New to the two environments this works in? Start with Claude Cowork vs Claude Code: What's the Difference?.
- See how Opus and Fable complement each other in practice in Claude Opus 5: Fable 5 Killer or Benchmark Hype?.


