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 skills add stdevMac/grok-in-codex --skill grok-routinggit clone --depth 1 https://github.com/stdevMac/grok-in-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/stdevmac/grok-in-codex/grok-routing)<a href="https://agentmods.dev/skills/stdevmac/grok-in-codex/grok-routing"><img src="https://agentmods.dev/badge/skills/stdevmac/grok-in-codex/grok-routing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stdevmac/grok-in-codex/grok-routing"><img src="https://agentmods.dev/badge/skills/stdevmac/grok-in-codex/grok-routing.svg" alt="Reviewed on agentmods" width="80" 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.01076 |
| Opus 5.5 | $0.00006 | $0.00430 |
| Sonnet 5.5 | $0.00003 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- grok-routing — 100% identical, 2 lines differ
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) |
| 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.
- 1mo ago First seen · 109 lines · 16 tokens per session scan A 2c1acbbdcb9f
grok-routing is a skill published in the GitHub repository stdevMac/grok-in-codex (28 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,076 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
ima2
Use the ima2-gen CLI/server to generate, edit, inspect, and manage local AI image generation jobs.
ima2-front
Frontend implementation skill for ima2 users. Use for any frontend, web UI, or visual implementation work — building, styling, or redesigning pages/components, responsive layouts, motion, component architecture, and production-surface polish. Pairs with ima2-uiux: load it first when design direction is vague; this…
ima2-uiux
Design direction discovery and UX judgment for ima2 users. Use for UI/UX direction and design judgment — vague visual briefs, onboarding, empty/error/loading states, layout vocabulary, typography breaks, favicons, logos, and brand identity choices. Pairs with ima2-front: this skill decides the design direction, then…
grok-routing
When to reach for Grok Build rather than doing the work in Claude Code — the routing tiers (manual, second-opinion, reach, offload-first, delegate-write), what each one covers, what it costs, and how to call it. Load this before offloading work, before asking for a second opinion, and before delegating anything to…
grok-result-handling
Internal guidance for presenting Grok helper output back to the user.
local-image-gen
A local command-line tool for generating or editing images with Codex, Grok, or Gemini/Antigravity accounts and optional API keys.