Fable Orchestrator plugin
A plugin keeps the strong model on planning, giving bulk work to Sonnet and hard slices to Opus so usage limits drain slower
- 82 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The plugin hooks session start, prompts and tool calls, denies some edits and injects text into the context
- Metrics are written to disk under `~/.claude/fable-orch/` and do not include prompt text
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/fable-orchestratorDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin hooks session start, prompts and tool calls, denies some edits and injects text into the context
- Metrics are written to disk under `~/.claude/fable-orch/` and do not include prompt text
This is third-party code. Review the repository files before installing.
What it does
Fable Orchestrator is a Claude Code plugin that keeps a strong model on planning and decisions while handing execution to named workers. Bulk work goes to Sonnet 5.5 and hard slices such as architecture, irreversible migrations and security review go straight to Opus 5.5. Effort never exceeds `high`. When a tier is not enough the task moves to the next model. Four mechanisms ship. A chair profile is injected at session start, a solo guard denies the third file edit with no worker spawned, a naming gate asks for a name on a large spawn, and a one-line reminder rides on every prompt. Workers report in at most 40 lines and the rest goes to disk.
Who it is for. Claude Code users with subscription limits who run long sessions on a strong model and want to spend it only on planning.
Good fit when
- You run a multi-hour session and fear burning the costly model limit on routine file edits
- Execution splits into many independent tasks that are easy to hand to Sonnet by spec
- Part of the work needs architecture or migration decisions and is best given to Opus directly
- You want to watch workers in tmux panes and follow their work
- The Fable limit ran out and the chair must move to Opus with `claude --continue --model opus`
Not a fit when
- The task is small and fits a couple of edits: worker overhead does not pay off
- You lack Python 3.10 and macOS or Linux: the hooks use `ps` and `tmux`
- You switch models inside a session with `/model`: the hooks cannot see it
- Your session does not use the Fable, Sonnet and Opus models from the description
Example request
Plan the database schema migration, hand routine work to Sonnet and give the irreversible steps to OpusLimitations
The solo guard counts only `Edit`, `Write`, `MultiEdit` and `NotebookEdit` calls, so a chair that writes files through `Bash` never trips it. Each gate fires once per session and a model can ignore the nudge. The `/model` command is invisible to the hooks: move the chair by relaunching with `--model` or pin `FABLE_ORCH_PROFILE`. It needs Python 3.10 or newer and macOS or Linux. Metrics without prompt text go to `~/.claude/fable-orch/metrics.jsonl`, and `FABLE_ORCH_METRICS=0` turns them off.
How to disable. Remove the plugin through `/plugin`. For a manual install remove the four hooks from `~/.claude/settings.json` and the copied scripts from `~/.claude/hooks/`. Single mechanisms switch off with `FABLE_ORCH_SOLO_GUARD=0` and `FABLE_ORCH_REMIND=0`.
FAQ
How do I install the Fable Orchestrator plugin?
In Claude Code run `/plugin marketplace add Rylaa/fable5.2-opus5.5-orchestrator` and `/plugin install orchestrator@fable-orchestrator`, then restart the client because hooks load at start.
What if the Fable limit runs out?
Relaunch with `claude --continue --model opus`. The Opus profile keeps the same rules while the Fable tier rests. Do not use `/model`: the hooks cannot see it.
Why set `CLAUDE_CODE_SUBAGENT_MODEL=sonnet`?
It protects against a worker spawned without a model, which would otherwise get Fable, the costliest. With it the worker runs on Sonnet.
How do I watch the workers?
Start `claude` inside tmux: named workers appear as panes in your window. Unnamed ones are visible only after they return.
Can I turn the solo edit guard off?
Yes, `FABLE_ORCH_SOLO_GUARD=0` disables it entirely and `FABLE_ORCH_SOLO_EDITS` changes the threshold, the third edit by default.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin with four working-method skills: classify the task, act in steps, verify the result and generate domain adapters
A skill that makes the lead Claude model a foreman: it plans work, hands tasks to worker agents and verifies the result itself.
A skill that turns the main Claude Code session into a dispatcher: tasks go to background subagents and the chat never blocks.
A Claude Code plugin that hands coding tasks to Codex agents, monitors them and verifies the results independently
A Claude Code plugin that injects Anthropic guide rules into sessions, with the fable command expanding a vague ask
A Claude Code plugin where the main model plans and signs off while search, edits and verification go to roles running on cheaper models
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Fable Orchestrator (this card) | no | 82 | |
| Orchestrator | no | 119 | a skill describing orchestration; here hooks enforce delegation and count the chair edits |
| OpenCode Agent Orchestration Kit | no | 153 | an orchestration kit for OpenCode; here a Claude Code plugin with model profiles and escalation |
README in short
The README draws the division of labor between the chair and the Sonnet and Opus workers and describes the four plugin mechanisms. It then covers changing the chair, manual install without the plugin, settings variables, upgrading to 0.17.2, tests and limitations.