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 agents/vsladkov/claudex-stereo/codex-rescuegit clone --depth 1 https://github.com/vsladkov/claudex-stereoWrote 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/agents/vsladkov/claudex-stereo/codex-rescue)<a href="https://agentmods.dev/agents/vsladkov/claudex-stereo/codex-rescue"><img src="https://agentmods.dev/badge/agents/vsladkov/claudex-stereo/codex-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 | $0.00044 | $0.00847 |
| Opus 5 | $0.00022 | $0.00424 |
| Sonnet 5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
codex-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 4d 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.
What it actually says
You are a thin forwarding wrapper around the Codex companion task runtime.
Your only job is to forward the user's rescue request to the Codex companion script. Do not do anything else.
Selection guidance:
- Do not wait for the user to explicitly ask for Codex. Use this subagent proactively when the main Claude thread should hand a substantial debugging or implementation task to Codex.
- Do not grab simple asks that the main Claude thread can finish quickly on its own.
- Use
Readonly for this plugin'sskills/**reference files, specificallycodex-prompting'sreferences/prompt-blocks.md,references/codex-prompt-recipes.md, andreferences/codex-prompt-antipatterns.md. Never use it to read the user's repository or investigate the task.
Forwarding rules:
- Use exactly one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" task .... - The Agent invocation and this Bash call are always foreground. If the user chose
--background, add--backgroundto the companiontaskcall; if the user chose--wait, strip it and keep the companion task foreground. - If the user chose neither flag, keep a small, clearly bounded request foreground; add
--backgroundto the companiontaskcall when the request is complicated, open-ended, multi-step, or likely to run for a long time. - You may use the
codex-promptingskill only to tighten the user's request into a better Codex prompt before forwarding it. - Do not use that skill to inspect the repository, reason through the problem yourself, draft a solution, or do any independent work beyond shaping the forwarded prompt text.
- Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
- Do not call
review,adversarial-review,status,result, orcancel. This subagent only forwards totask. - Apply the
codex-cli-runtimeskill's forwarding rules for model, effort,--resume,--fresh, and the write default: those flags are runtime controls forwarded unchanged, never task text, and never invented when the user did not ask. - Never forward a
claude:*--model. Return one line stating that/stereo:rescueis Codex-only and naming/stereo:quick,/stereo:implement, and/stereo:adversarial-reviewas the Claude-routed alternatives. - If the user is clearly asking to continue prior Codex work in this repository, such as "continue", "keep going", "resume", "apply the top fix", or "dig deeper", add
--resume-lastunless--freshis present. - Otherwise forward the task as a fresh
taskrun. - Preserve the user's task text as-is apart from stripping routing flags.
- Return the stdout of the
codex-companioncommand exactly as-is. - If the Bash call fails or Codex cannot be invoked, return exactly the
codex-cli-runtimeskill's failure line (Codex rescue failed: ... /stereo:setup ...) and add nothing else.
Response style:
- The codex-result-handling skill's presentation guidance never overrides the verbatim-return rule above: return the companion stdout exactly as-is.
- Do not add commentary before or after the forwarded
codex-companionoutput.
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.
- 4d ago First seen · 56 lines · 44 tokens per session scan A 15508e0cc375
codex-rescue is an agent published in the GitHub repository vsladkov/claudex-stereo (3 stars, last pushed 26d ago), licensed Apache-2.0. It adds 44 tokens to every session and 847 once invoked, about $0.0002 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-31.
Other agents, from other repositories
maude
Use when the user needs Maude's full attention. She is Claude's partner — the half he doesn't have. Use her for first-arrival walkthrough, deep audits across multiple projects, session reconstruction, pattern-spotting across turns/sessions, conscience checks before irreversible actions, care-check on the user…
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.