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 skills add Beaulewis1977/claude-plugin-for-codex --skill claude-rescuegit clone --depth 1 https://github.com/Beaulewis1977/claude-plugin-for-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/skills/beaulewis1977/claude-plugin-for-codex/claude-rescue)<a href="https://agentmods.dev/skills/beaulewis1977/claude-plugin-for-codex/claude-rescue"><img src="https://agentmods.dev/badge/skills/beaulewis1977/claude-plugin-for-codex/claude-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/skills/beaulewis1977/claude-plugin-for-codex/claude-rescue"><img src="https://agentmods.dev/badge/skills/beaulewis1977/claude-plugin-for-codex/claude-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.00034 | $0.00400 |
| Opus 5 | $0.00017 | $0.00200 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
claude-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 10d 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
Claude Rescue
Delegate one bounded engineering task to Claude, preserving the user's chosen permission and routing boundaries.
Permissions
Write-capable rescue defaults to acceptEdits. Add --read-only when the user
asks for diagnosis only; that selects plan permission and safe-mode. Add
--bypass-permissions only for an explicit user request for unrestricted
permissions or an unambiguous equivalent. Never infer bypass from urgency or
difficulty.
Workflow
- Define the goal, failure symptoms, relevant context, constraints, allowed
scope, and required tests. Classify routine or bounded work as normal,
substantial reasoning as hard, and the most complex or high-stakes work as
very-hard. Pass that classification with
--tier. Explicit model and effort selections always win. - Resolve
<plugin-root>/scripts/claude-companion.mjsto an absolute path. - Make exactly one runtime invocation. Runtime action:
rescue. - Pass
--cwdwith the current workspace and--jsonas separate arguments. Translate explicit background, wait, resume, fresh, routing, timeout, and permission requests into their dedicated flags. - Write the free-form task and context to stdin. Never place task text in an option, argument, or shell command. Use an argument array; never concatenate or interpolate values into a shell command. Use the execution tool's separate stdin channel; if it exposes an interactive process session, send the text there and explicitly close stdin before waiting.
- Report Claude's output separately. Inspect changed files and verification evidence before accepting the work; do not duplicate or silently redo the delegated implementation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 39 lines · 34 tokens per session scan A c8975688ad36
claude-rescue is a skill published in the GitHub repository Beaulewis1977/claude-plugin-for-codex (3 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 400 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 skills, from other repositories
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…
root-cause-investigator
Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.
github-issue-manager
Classifies a user request as Bug, Compatibility, Feature, Question, or Task for the explyt/spring-plugin GitHub repo, lightly researches the relevant codebase, searches similar existing issues, and either reports an existing issue or creates a correctly titled and labeled one following the repository issue forms. Use…
github-bugs-triage
Triages the open bug queue of the explyt/spring-plugin GitHub repository: fetches the oldest open plugin-bug and compatibility issues, refines titles, suggests labels and priorities with evidence, detects duplicates, and writes a structured triage table. Use when asked to triage spring-plugin bugs, review the bug…
create-issue
Transitional alias — prefer /prflow:specs, which runs the same issue-drafting pipeline. Use when a rough user story, bug report, feature idea, piece of feedback, or an implementation plan should be recorded as a GitHub issue rather than built right now. This command name is retained so existing /prflow:create-issue…
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…