Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/luckeyfaraday/codex-router/codexnpx skills add luckeyfaraday/codex-router --skill codexgit clone --depth 1 https://github.com/luckeyfaraday/codex-routerWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00113 | $0.01997 |
| Opus 5 | $0.00056 | $0.00999 |
| Sonnet 5 | $0.00023 | $0.00399 |
| Haiku 4.5 | $0.00011 | $0.00200 |
Grade A, and why
codex scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Offload — route heavy work to GPT-5.6
You are the orchestrator and reviewer. Codex is the background worker. Select its model for the task, write a precise brief, launch Codex non-interactively, keep working or wait, then review and verify what it produced. You own final quality — never present Codex's output to the user unreviewed.
When to offload (and when not to)
Offload when the task is heavy but well-specified: large refactors or renames across many files, bulk migrations (API, framework, syntax), generating boilerplate-heavy features from a clear spec, fixing a long list of similar test failures or lint errors, or any task the user explicitly asks to send to Codex or a GPT worker.
Keep it yourself when the task is small (faster to just do it), requires conversation context or user judgment mid-flight, is design/architecture work, or touches secrets and credentials.
1. Preflight (once per session)
codex login status
codex --version
codexnot found → tell the user:npm install -g @openai/codex- Not logged in → tell the user to run
! codex login(interactive; you cannot do it for them) - GPT-5.6 requires Codex CLI 0.144.0 or newer. If it is older, tell the user to update Codex before routing to GPT-5.6.
2. Select the worker model
Honor an explicit model request from the user. Otherwise, honor CODEX_ROUTER_MODEL when it is
set; it is the user's configured default. If neither chooses a model, route as follows:
| Model ID | Use for | Typical effort |
|---|---|---|
gpt-5.6-sol |
Hard, ambiguous-but-implementable, cross-cutting, or long-horizon coding work where quality is worth additional time and cost | high or xhigh; use max only when the account supports it |
gpt-5.6-terra |
The default: well-specified refactors, migrations, and substantial everyday implementation work | high |
gpt-5.6-luna |
Tightly bounded, repetitive, high-throughput work where latency and cost matter more than frontier reasoning | medium or high |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 159 lines · 113 tokens per session scan A 24fc57cb6cd0
codex is a skill published in the GitHub repository luckeyfaraday/codex-router (6 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 1,997 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
kimi-first
Route implementation work-orders to Kimi k3 lanes via the Kimi Code CLI; Claude specs, orchestrates, reviews, verifies. Use when a task is a frozen-spec build, mechanical migration, test fill, bulk sweep, or CI fix — anything that reads as a work order rather than a design problem.
tao
Orchestrate large, multi-stage, or long-running engineering work with a persistent strong Project Lead, reusable economy Workers, optional review, and repository-backed handoffs. Use for model-cost-aware execution, explicit tiered-agent commands, or continuation when .tiered-agent state exists. Do not start the full…
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
mcp-builder
Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.
mcp-discovery
Prefer a matching zero-environment local MCP server for specialized tasks, even when built-in shell commands or custom code could also solve them.
cao-plugin
Create a new CAO (CLI Agent Orchestrator) plugin. Use this skill whenever the user wants to add a plugin that reacts to CAO lifecycle or messaging events, scaffold a plugin package, understand plugin requirements, or integrate an external system (Discord, Slack, dashboards, logging, metrics) with CAO. Also use when…