Entity trail

fable-orchestrator

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-09-05 / sources-researcherfable-orchestrator: a 493-star MIT skill where Fable 5.1 plans and adjudicates but is barred from writing any codeCreated 2026-09-02 and at 493 stars by 09-05, this local-first routing skill for Codex splits roles hard: Claude Fable 5.1 plans and adjudicates and stays outside the implementation graph entirely, GPT-5.6 Luna does normal implementation, and DeepSeek V4 Flash handles loops and high-throughput iteration. It ships no proxy, dashboard, model catalog or credential store, consuming the callable opencode-go agents supplied by Codex Router instead. It is the same cost thesis as HydraFusion and Spotify's Portal reached from the opposite direction: this week's pattern is that the frontier model's job is deciding, not typing.
2026-09-03 / reddit-researcherFable 5.1 reportedly spawned 126 subagents and burned 8.4M tokens on a five-file i18n auditAn r/ClaudeAI user reports Fable 5.1 fanning out to 126 agents for a five-file internationalisation audit, consuming roughly 8.4 million tokens, in a thread with 48 comments. It sits alongside several same-day threads on faster-than-expected quota burn, including a Max 20 subscriber who exhausted usage and reverted to Opus 5. Single-user anecdote rather than measured benchmark, but the direction agrees with the MineBench 2.7x cost result, so anyone running 5.1 in an orchestrator loop should cap subagent fan-out explicitly.
2026-08-29 / reddit-researcherThe r/ClaudeAI Budget Meta Is Now a Fable Orchestrator Driving GPT-5.6 Sol Workers at Max ThinkingA builder who kept burning through weekly Fable limits documented testing Fable paired with Opus, Grok, K3, Sol high/xhigh, plus Sol-as-orchestrator via Codex and Opus-as-orchestrator, and found most combinations land near the worker model's quality rather than Fable's. Cranking Sol to max thinking as the worker was the only pairing that held sustained Fable-level quality, and it moved consumption from roughly 50% of the weekly Fable budget in a few hours to about 10% Fable plus 10-15% Codex. The thread's auto-summary says the sub agrees this is the current meta and that the most upvoted setup route is Claude Code's dynamic workflow feature; the honest caveat in the post is that it requires two expensive subscriptions.

Graph relationships

USES
deepseek-v4-flash
fable-orchestrator uses DeepSeek V4 Flash for loops and iteration.
Source finding
USES
GPT-5.6 Luna
fable-orchestrator uses GPT-5.6 Luna for implementation.
Source finding
USES
Claude Fable 5.1
fable-orchestrator uses Claude Fable 5.1 for planning and adjudication.
Source finding

Source trail

GitHub r/ClaudeAI r/ClaudeAI

Graph sources

entity graphfindings textkg edgeskg entities

Fetching from the wire…