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/bigu1/grok-plugin-codex/grok-routingnpx skills add bigu1/grok-plugin-codex --skill grok-routinggit clone --depth 1 https://github.com/bigu1/grok-plugin-codexWrote 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/bigu1/grok-plugin-codex/grok-routing)<a href="https://agentmods.dev/skills/bigu1/grok-plugin-codex/grok-routing"><img src="https://agentmods.dev/badge/skills/bigu1/grok-plugin-codex/grok-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.00016 | $0.01088 |
| Opus 5 | $0.00008 | $0.00544 |
| Sonnet 5 | $0.00003 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
grok-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.
This is a copy
100% identical to grok-routing — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to call Grok
Prefer Grok MCP tools
- Substantial debugging after Codex is stuck
- Second-opinion implementation of a non-trivial change
- Best-of-N alternative approaches (
bestOfN) - Risky edits that should land in a worktree (
worktree) - Ambiguous architecture →
grok_planthen implement, orgrok_design - Multi-PR delivery from a design doc →
grok_execute_plan - Named multi-agent recipes →
grok_workflow - PR CI/review babysitting →
grok_babysit - Image/video generation (
grok_image,grok_video) - Documents (
grok_documentwithtypepdf|docx|pptx) - Structured or adversarial code review before shipping
- Long-running investigation better as a background job
Prefer staying in Codex
- Quick questions, renames, one-line fixes
- Tiny edits with obvious answers
- Pure conversation without repo mutation
Intent → tool
| User intent | Prefer |
|---|---|
| Stuck on a bug / implement a fix | grok_rescue (+ worktree; check is prompt-side on CLI 1.0.x) |
| Unclear approach before coding | grok_plan |
| Architecture / design doc + PR plan | grok_design |
| Ship a design doc’s PR DAG | grok_execute_plan (or latest=true after design) |
| Multi-dimension structured fan-out | grok_workflow |
| Ship quality on a branch/PR | grok_review (+ postPending for GH) |
| Challenge design assumptions | grok_adversarial_review |
| Watch / fix open PRs | grok_babysit |
| Deck / PDF / Word | grok_document |
| Brand stills / clips | grok_image / grok_video |
| Find past Grok work | grok_sessions |
Depth pipeline (multi-PR / ambiguous product work)
Prefer this sequence over a single giant rescue:
grok_plan— explore + plan.md when the approach is unclear (artifacts under.grok-plans/).grok_design— consensus design doc + PR Plan → artifacts under.grok-designs/.grok_execute_planwithlatest=true(or explicitdesignDoc) — implement the PR DAG in worktrees.grok_review/grok_babysit— quality and CI/review loop.
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 · 109 lines · 16 tokens per session scan A 728669f4e3ec
grok-routing is a skill published in the GitHub repository bigu1/grok-plugin-codex (0 stars, last pushed 12d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,088 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to grok-routing, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
gpt-5-4-prompting
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Grok Codex plugin.
codex-result-handling
Internal guidance for presenting Codex helper output back to the user.
grok-subagent
Delegate bounded coding, investigation, review, implementation, and real-time X/Reddit/web research tasks from Codex to the locally authenticated Grok Build CLI. Use when the user asks Codex to consult Grok, use Grok as a subagent, compare independent model conclusions, spend SuperGrok quota on useful project work…
delegate-to-grok
Delegate coding, repository inspection, comparisons, web research, and public X search from Codex to the locally installed Grok Build CLI on Windows. Use when a user asks to run or consult Grok, resume Grok Build authentication, compare Codex and Grok, inspect or modify a project with Grok, or perform public X…
grok-prompting
Internal guidance for composing Grok Build prompts for coding, review, diagnosis, and research tasks inside the Grok Claude Code plugin.
grok-bridge
Delegate any substantial local task to Grok Build as one durable logical job, in a repository or a non-repository workspace, and retrieve its genuine final result across turn, token, context, and caller-session boundaries. Use when the user asks for Grok/Grok Build, an independent builder/tester/reviewer/researcher…