darasoba/claude-model-relay — explained in plain English
Analysis updated 2026-05-18
Route architectural or security-sensitive code changes to a stronger model automatically
Keep routine, well-specified coding tasks on a cheaper model to save cost
Get an independent adversarial review of a code change before accepting it
Avoid silent quality loss when a model hits its usage limit mid-task
| darasoba/claude-model-relay | anil-matcha/open-poe-ai | arata-ae/purupurupngtuber | |
|---|---|---|---|
| Stars | 4 | 4 | 4 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | — | 2026-06-25 | — |
| Maintenance | — | Active | — |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 3/5 | 3/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Works best with access to all the models in the fallback chains, such as Fable 5, Opus, and Sonnet.
Claude Model Relay is a small set of skills and subagents for Claude Code that splits a coding task across three different AI models instead of using one model for everything. The idea is that the most expensive, most capable model is best spent on planning and on reviewing the finished work, while a mid-tier model can handle the actual writing of code once it has a clear plan to follow. The process runs in three stages. First, a read-only planner using Fable 5 looks at the real codebase, writes a step-by-step plan naming exact files and pieces of code, and classifies the task as either high complexity, meaning architectural changes, concurrency, security work, or an unclear root cause across many files, or standard complexity, meaning a contained and well-specified change. Second, an implementer stage carries out the plan, using Opus 4.8 for high complexity tasks and Sonnet 5 for standard ones, then runs the plan's own verification step and reports honestly if the actual work turned out to differ from the plan. Third, a separate read-only reviewer, again using Fable 5, independently re-checks the verification and the real code changes, then returns either an approval or a request to revise, capped at two revision rounds before the disagreement gets handed back to the person who asked for the change. Because each model has its own usage limits, the project also defines fallback chains, so if one model runs out of usage the task moves to a specified backup model instead of quietly failing, and the tool always reports out loud whenever this kind of fallback happens. Installation is a single command that copies one skill file and three subagent files into Claude Code's configuration folders, with alternative install paths through a Claude Code plugin or a manual git clone. The project is released under the MIT license, which allows free use, including commercial use.
A Claude Code skill that splits coding tasks across three AI models, one for planning, one for writing code, and one for reviewing, with automatic fallback if a model hits its usage limit.
Mainly JavaScript. The stack also includes Claude Code, Fable 5, Opus.
Use freely for any purpose, including commercial use.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.