agentmods.dev

rescue

A command that sends an investigation, requested fix, or follow-up task to a Codex rescue helper.

In plain words
What is it for?
Use it for debugging investigations, explicit code fixes, and follow-up work that needs a delegated Codex task.
Why use it?
It delegates the requested work to a separate Codex subagent while preserving the original request and supporting foreground or background execution.

Command

33k 1mo ago A scan 20 tokens original Apache-2.0
View the source file openai/codex-plugin-cc
Install

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.

agentmods
npx agentmods add commands/openai/codex-plugin-cc/rescue
Clone the repo
git clone --depth 1 https://github.com/openai/codex-plugin-cc
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 927 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00927
Opus 5 $0.00010 $0.00464
Sonnet 5 $0.00004 $0.00185
Haiku 4.5 $0.00002 $0.00093

Measured yesterday against content hash 089207554cc3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

  • rescue — 95% identical, 3 lines differ
  • rescue — 92% identical, 12 lines differ
  • task — 88% identical, 44 lines differ
  • rescue — 88% identical, 42 lines differ
  • rescue — 88% identical, 52 lines differ
  • rescue — 86% identical, 33 lines differ
  • rescue — 84% identical, 6 lines differ
  • rescue — 80% identical, 46 lines differ
plugins/codex/commands/rescue.md · 50 lines

What it actually says

Invoke the codex:codex-rescue subagent via the Agent 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 the codex:codex-rescue subagent in the background.
  • If the request includes --wait, run the codex:codex-rescue subagent in the foreground.
  • If neither flag is present, default to foreground.
  • --background and --wait are execution flags for Claude Code. Do not forward them to task, and do not treat them as part of the natural-language task text.
  • --model and --effort are runtime-selection flags. Preserve them for the forwarded task call, 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 Claude session by running:
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs" task-resume-candidate --json
  • If that helper reports available: true, use AskUserQuestion exactly once to ask whether to continue the current Codex thread or start a new one.
  • The two choices must be:
    • Continue current Codex thread
    • Start 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 --resume before routing to the subagent.
  • If the user chooses a new thread, add --fresh before 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 call to invoke node "${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 --effort unset 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 to gpt-5.3-codex-spark.
  • Leave --resume and --fresh in the forwarded request. The subagent handles that routing when it builds the task command.
  • 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.
Changes

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.

  1. yesterday First seen · 50 lines · 20 tokens per session scan A 089207554cc3

Subscribe to this mod's changes

rescue is a command published in the GitHub repository openai/codex-plugin-cc (32,553 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 927 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-30.

DebuggingPlanningResearch
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens