Charlie HillsFree guide · Claude & Claude Code
Make Fable 5.2 last all week: The token saving guide
The three steps that stop Fable 5.2 eating your Claude limit: the planner prompt, the Haiku subagent file, when to /clear, plus /usage and what each plan gets.
Charlie Hills Added 13 November 2026 · Free
What’s inside
- 1The run order
- 2Let Fable do the thinking, not the typing
- 3Hand the grunt work to Haiku
- 4Type /clear when you switch jobs
- 5See what is eating your usage
- 6What each plan gets
The run order
|
Step |
What you do |
How often |
|
1. Fable plans and reviews |
Start the job with the planner prompt |
Every job |
|
2. Haiku does the routine work |
Create the grunt-worker subagent |
Once per project |
|
3. Clear between jobs |
Type /clear when you switch to something new |
Every switch |
|
Check |
Type /usage to see what is using your limit |
Any time |
Step 1: Let Fable do the thinking, not the typing
Pick Fable 5.2, then paste this and swap the last line for your own job. Fable writes the plan, hands each routine step to the worker and checks what comes back.
Plan this job before you do anything. Break it into small steps, hand every routine step to the grunt-worker subagent, then check each result against your plan. Do none of the routine work yourself.
The job: [your job]What you should get back, and the check
A short plan first, then the worker running the routine steps, then Fable checking each result against the plan.
The check: if Fable starts doing a routine step itself, reply: "Hand that step to grunt-worker."
That’s the first part. The rest of this guide is free too.
