Claude Fable 5
Turn One Model Into a Team
Fable 5 is the model you bring in to lead: read the repo, shape the work, write the plan, and hand clean tasks to specialist models that execute. Stop paying frontier prices to watch it type. This book hands you the split-stack system as a build you own. Run your first Fable audit in twenty minutes, and by the weekend Fable is writing plans, Sonnet and Opus are executing handoffs, and your repo has a working /architect router. The last chapter ships one real project three ways and reads the receipt to the token. Every command runs, tested before it ships, with a free companion GitHub repo that needs no API key.
Fable 5 is not just another chat box. It is the model you bring in when a project needs taste, strategy, judgment, and a plan strong enough for other models to execute. The builders who figured it out early stopped asking one model to do everything. They made Fable read the repo, shape the work, write the plan, and hand execution to the right specialist. One model leads. The team builds. Prompts, plans, contracts, routers, and receipts become reusable assets you carry into the next project. This is 180 pages of dense, runnable, code-first build, with a free companion GitHub repo that installs the /architect router into your own Claude Code and ships a real invoicing service to run your first audit against.
What You'll Build
Why Fable earns its keep leading, not typing, and the split-stack rule that keeps frontier cost off your busywork.
The model roster: which seat leads, builds, reviews, and types, and what each one actually costs to run.
Credits, subscription plans, and API pricing worked out so you know what a project costs before you start.
Run your first Fable audit in twenty minutes: point it at a repo and get back a work map you can act on.
Turn Fable's judgment into an executable plan.md with a files-touched list a specialist model can pick up cold.
The single file that lets an architect model brief a builder model with zero context loss.
Supervise a specialist executor cheaply, catch drift early, and escalate to Fable only when it's worth the spend.
Use Fable for one senior review pass on the finished work, with no infinite fix-me loops.
What to do when Fable refuses: route the task to another executor without fighting the safety wall.
A one-command router that sends each task to the right model seat automatically.
Ship one real project three ways and read the metered ledger: split-stack vs all-Fable vs all-Opus, to the token.
Wire every piece into a portable model-team repo that outlives Fable and carries into your next project.