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/0xtitanas/codex-tier-routing/model-routingnpx skills add 0xTitanas/codex-tier-routing --skill model-routinggit clone --depth 1 https://github.com/0xTitanas/codex-tier-routingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/0xtitanas/codex-tier-routing/model-routing)<a href="https://agentmods.dev/skills/0xtitanas/codex-tier-routing/model-routing"><img src="https://agentmods.dev/badge/skills/0xtitanas/codex-tier-routing/model-routing.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00022 | $0.01875 |
| Opus 5 | $0.00011 | $0.00937 |
| Sonnet 5 | $0.00004 | $0.00375 |
| Haiku 4.5 | $0.00002 | $0.00187 |
Grade A, and why
model-routing 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 5d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model routing
Agent profiles describe requested behavior. They do not prove which model, effort level, sandbox, or working directory a child process actually used. Treat route selection as verified only when the active Codex host supplies the observation or the bundled dispatcher returns a passing local receipt.
Check capability first
Use one of these paths:
- A Codex surface that can select a registered profile from
agents/and exposes host-controlled execution details. - The installed local dispatcher at
${CODEX_HOME:-$HOME/.codex}/bin/codex-tier.
If neither path can select and verify the requested route, keep the work in the parent session. A role name in a prompt or response is not route evidence.
Ultra and host-provided spawning
Ultra mode or another Codex surface may expose a host-provided generic spawn
tool that is separate from the local dispatcher. Do not infer that such a child
used one of this project's routes. Unless the host itself selects the registered
profile and returns equivalent execution evidence, use codex-tier for the
delegation or keep the work in the parent.
Strict mode disables the documented native multi_agent feature for new
sessions using the selected Codex home. It cannot intercept a separate tool
injected by a host application. Output from that tool must not be labeled with a
route, model, effort, sandbox, lineage, or receipt from this project.
Local dispatcher
Run the zero-model-call probe before dispatching work:
"${CODEX_HOME:-$HOME/.codex}/bin/codex-tier" probe
Also validate the active model/effort mapping without a model call:
"${CODEX_HOME:-$HOME/.codex}/bin/codex-tier" policy-check
policy-check must pass. It reports the active policy hash, resolved routes,
accepted effort values, and model_access: not_checked. Policy syntax is not
account entitlement; run a bounded canary for every changed route.
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.
- 5d ago First seen · 193 lines · 22 tokens per session scan A 6fbfaa6ddbb3
model-routing is a skill published in the GitHub repository 0xTitanas/codex-tier-routing (1 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 1,875 once invoked, about $0.0001 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
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…