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 commands/jinxlzc/grok-codex-plugin/setupgit clone --depth 1 https://github.com/jinxlzc/grok-codex-pluginWhat 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.00017 | $0.00302 |
| Opus 5 | $0.00009 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
setup 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.
This is a copy
88% identical to setup — 8 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.
What it actually says
Run:
node "${GROK_PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs" setup --json $ARGUMENTS
If the result says Codex is unavailable and npm is available:
- Use
AskUserQuestion(Grok:ask_user_question) exactly once to ask whether Grok should install Codex now. - Put the install option first and suffix it with
(Recommended). - Use these two options:
Install Codex (Recommended)Skip for now
- If the user chooses install, run:
npm install -g @openai/codex
- Then rerun:
node "${GROK_PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs" setup --json $ARGUMENTS
If Codex is already installed or npm is unavailable:
- Do not ask about installation.
Output rules:
- Present the final setup output to the user.
- If installation was skipped, present the original setup output.
- If Codex is installed but not authenticated, preserve the guidance to run
codex login.
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 · 38 lines · 17 tokens per session scan A 246a823534b6
setup is a command published in the GitHub repository jinxlzc/grok-codex-plugin (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 17 tokens to every session and 302 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to setup, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
critique
Run a Grok Build critique that challenges the implementation approach and design choices.
check
Check whether the local Grok Build CLI is ready for the Claude Code bridge.
review
Run a read-only Grok code review against local git state.
adversarial-review
Run a skeptical, adversarial Grok code review against local git state.
rescue
Delegate a coding, debugging, or review task to the Grok CLI as a parallel worker.
setup
Check whether the local Grok CLI is installed, signed in, and ready to delegate to.