Score7.3
Popularity60.0
Risknone
TierSilver
Score breakdown
Usefulness7.0
Novelty8.0
Momentum6.0
Maturity6.6
Open-source/build8.4
Evidence7.2
Workflow potential8.8
Setup ease8.8
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers running Claude Code with a codex subscription who want to stop burning premium tokens on the parts of the job a cheaper agent already does fine. Clone the repo into `~/.claude/skills/arbitrage` (or `~/.codex/skills/arbitrage`), enable the skill, and watch the premium model hand all code-writing to codex while it stays focused on planning and review.
Who should use it
developers running Claude Code with a codex subscription who want to stop burning premium tokens on code-typingteams who want a spec-first split where the premium model owns planning + review and a cheaper model owns implementationagent developers who want a SKILL.md pattern that dispatches implementation to `codex exec` in the backgroundanyone who wants a two-strikes escape hatch that takes work back when the cheaper model misses the bar
Who should skip it
Skip if the source link, docs, or setup requirements do not match your workflow.
Risk explanation
No inherent user-impacting risk is flagged from the captured evidence.
Evidence links
Closest alternatives / related signals
claude-codecodextoken-arbitrageroutingagent-skillscost-optimizationspec-drivenmit