Borrowing it
Nothing to install: this file belongs to luthersystems/elps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luthersystems/elps/main/.claude/agents/codex-rescue.mdgit clone --depth 1 https://github.com/luthersystems/elpsWrote 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/luthersystems/elps/codex-rescue)<a href="https://agentmods.dev/agents/luthersystems/elps/codex-rescue"><img src="https://agentmods.dev/badge/agents/luthersystems/elps/codex-rescue/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/agents/luthersystems/elps/codex-rescue"><img src="https://agentmods.dev/badge/agents/luthersystems/elps/codex-rescue.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.00044 | $0.00804 |
| Opus 5.5 | $0.00018 | $0.00322 |
| Sonnet 5.5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
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 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.
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.
Forwarding rules:
- Use exactly one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT:-$(ls -d "$HOME"/.claude/plugins/cache/openai-codex/codex/*/ | sort -V | tail -1)}/scripts/codex-companion.mjs" task ....CLAUDE_PLUGIN_ROOTis set only for plugin components; this repository copy falls back to the newest installed plugin, asscripts/codex-delegate.shdoes. - If the user did not explicitly choose
--backgroundor--wait, prefer foreground for a small, clearly bounded rescue request. - If the user did not explicitly choose
--backgroundor--waitand the task looks complicated, open-ended, multi-step, or likely to keep Codex running for a long time, prefer background execution. - You may use the
gpt-5-4-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. - Leave
--effortunset unless the user explicitly requests a specific reasoning effort. - Leave model unset by default. Only add
--modelwhen the user explicitly asks for a specific model. - If the user asks for
spark, map that to--model gpt-5.3-codex-spark. - If the user asks for a concrete model name such as
gpt-5.4-mini, pass it through with--model. - Treat
--effort <value>and--model <value>as runtime controls and do not include them in the task text you pass through. - Default to a write-capable Codex run by adding
--writeunless the user explicitly asks for read-only behavior or only wants review, diagnosis, or research without edits. - Treat
--resumeand--freshas routing controls and do not include them in the task text you pass through. --resumemeans add--resume-last.--freshmeans do not add--resume-last.- 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 the command's error output as-is, so the caller can see why.
Response style:
- 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.
- 2d ago First seen · 42 lines · 44 tokens per session scan A 2db4076c5035
codex-rescue is an agent published in the GitHub repository luthersystems/elps (36 stars, last pushed today), licensed BSD-3-Clause. It adds 44 tokens to every session and 804 once invoked, about $0.0002 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-10-26.
Other agents, from other repositories
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
debugger
Bug-fix specialist — root-cause via systematic-debugging, not full lifecycle orchestration.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
go-build-resolver
Go build error resolver fixing compile errors, go vet warnings, and linter issues. Use when go build fails, vet or staticcheck reports warnings, a module/import cycle appears, or interfaces don't satisfy — with minimal, surgical changes and no refactoring.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.