Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jinxlzc/grok-codex-plugin/plugin install 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/commands/jinxlzc/grok-codex-plugin/rescue)<a href="https://agentmods.dev/commands/jinxlzc/grok-codex-plugin/rescue"><img src="https://agentmods.dev/badge/commands/jinxlzc/grok-codex-plugin/rescue.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.00020 | $0.00964 |
| Opus 5 | $0.00010 | $0.00482 |
| Sonnet 5 | $0.00004 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
rescue 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
92% identical to rescue — 12 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
Invoke the codex:codex-rescue subagent via the Agent / spawn_subagent tool (subagent_type: "codex:codex-rescue"), forwarding the raw user request as the prompt.
codex:codex-rescue is a subagent, not a skill — do not call Skill(codex:codex-rescue) (no such skill) or Skill(codex:rescue) (that re-enters this command and hangs the session). The command runs inline so the Agent tool stays in scope; forked general-purpose subagents do not expose it.
The final user-visible response must be Codex's output verbatim.
Raw user request: $ARGUMENTS
Execution mode:
- If the request includes
--background, run thecodex:codex-rescuesubagent in the background. - If the request includes
--wait, run thecodex:codex-rescuesubagent in the foreground. - If neither flag is present, default to foreground.
--backgroundand--waitare execution flags for Grok Build. Do not forward them totask, and do not treat them as part of the natural-language task text.--modeland--effortare runtime-selection flags. Preserve them for the forwardedtaskcall, but do not treat them as part of the natural-language task text.- If the request includes
--resume, do not ask whether to continue. The user already chose. - If the request includes
--fresh, do not ask whether to continue. The user already chose. - Otherwise, before starting Codex, check for a resumable rescue thread from this Grok session by running:
node "${GROK_PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs" task-resume-candidate --json
- If that helper reports
available: true, useAskUserQuestion(Grok:ask_user_question) exactly once to ask whether to continue the current Codex thread or start a new one. - The two choices must be:
Continue current Codex threadStart a new Codex thread
- If the user is clearly giving a follow-up instruction such as "continue", "keep going", "resume", "apply the top fix", or "dig deeper", put
Continue current Codex thread (Recommended)first. - Otherwise put
Start a new Codex thread (Recommended)first. - If the user chooses continue, add
--resumebefore routing to the subagent. - If the user chooses a new thread, add
--freshbefore routing to the subagent. - If the helper reports
available: false, do not ask. Route normally.
Operating rules:
- The subagent is a thin forwarder only. It should use one
Bash/run_terminal_commandcall to invokenode "${GROK_PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs" task ...and return that command's stdout as-is. - Return the Codex companion stdout verbatim to the user.
- Do not paraphrase, summarize, rewrite, or add commentary before or after it.
- Do not ask the subagent to inspect files, monitor progress, poll
/codex:status, fetch/codex:result, call/codex:cancel, summarize output, or do follow-up work of its own. - Leave
--effortunset unless the user explicitly asks for a specific reasoning effort. - Leave the model unset unless the user explicitly asks for one. If they ask for
spark, map it togpt-5.3-codex-spark. - Leave
--resumeand--freshin the forwarded request. The subagent handles that routing when it builds thetaskcommand. - If the helper reports that Codex is missing or unauthenticated, stop and tell the user to run
/codex:setup. - If the user did not supply a request, ask what Codex should investigate or fix.
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 · 50 lines · 20 tokens per session scan A 37321f1fd36f
rescue is a command published in the GitHub repository jinxlzc/grok-codex-plugin (1 stars, last pushed 23d ago), licensed Apache-2.0. It adds 20 tokens to every session and 964 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to rescue, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
login
Sign in to Grok Build CLI using the default install path.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.
delegate-codex
Delegate to local Codex CLI (Grok background task; live tools in task log).
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).