A command that sends an investigation, fix request, or follow-up task to OpenCode’s rescue assistant. It can run the task now or in the background, and can continue a previous rescue session.

Use it to investigate problems, apply an explicitly requested fix, or continue unfinished rescue work.

It lets a separate assistant handle troubleshooting or requested changes without making you manage the handoff yourself.

rescue — Command by tasict

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/tasict/opencode-plugin-cc/rescue

Clone the repo

git clone --depth 1 https://github.com/tasict/opencode-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 780 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.

Model	Per session	Once invoked
Fable 5	$0.00020	$0.00780
Opus 5	$0.00010	$0.00390
Sonnet 5	$0.00004	$0.00156
Haiku 4.5	$0.00002	$0.00078

Measured 2d ago against content hash 302d9abbd185, 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

rescue — 88% identical, 40 lines differ

plugins/opencode/commands/rescue.md · 50 lines

What it actually says

Route this request to the opencode:opencode-rescue subagent. The final user-visible response must be OpenCode's output verbatim.

Raw user request: $ARGUMENTS

Execution mode:

If the request includes --background, run the opencode:opencode-rescue subagent in the background.
If the request includes --wait, run the opencode:opencode-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 --agent 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 OpenCode, check for a resumable rescue session from this Claude session by running:

node "${CLAUDE_PLUGIN_ROOT}/scripts/opencode-companion.mjs" task-resume-candidate --json

If that helper reports available: true, use AskUserQuestion exactly once to ask whether to continue the current OpenCode session or start a new one.
The two choices must be:
- Continue current OpenCode session
- Start a new OpenCode session
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 OpenCode session (Recommended) first.
Otherwise put Start a new OpenCode session (Recommended) first.
If the user chooses continue, add --resume before routing to the subagent.
If the user chooses a new session, 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/opencode-companion.mjs" task ... and return that command's stdout as-is.
Return the OpenCode 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 /opencode:status, fetch /opencode:result, call /opencode:cancel, summarize output, or do follow-up work of its own.
Leave --agent unset unless the user explicitly asks for a specific agent (build or plan).
Leave the model unset unless the user explicitly asks for one.
Leave --resume and --fresh in the forwarded request. The subagent handles that routing when it builds the task command.
If the helper reports that OpenCode is missing or unauthenticated, stop and tell the user to run /opencode:setup.
If the user did not supply a request, ask what OpenCode 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.

2d ago First seen · 50 lines · 20 tokens per session scan A 302d9abbd185

Subscribe to this mod's changes

rescue is a command published in the GitHub repository tasict/opencode-plugin-cc (18 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 780 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.

Building agents Planning Research

verify

Adversarial spec-vs-implementation verification for a completed task. Dispatches the spec-mentor subagent with fresh context (no anchoring bias), parses its verdict (PASS / DRIFT / NEEDS-MARTY), and updates the verification queue. The v7.4.0 architectural replacement for a dedicated "mentor session.".

MartyBonacci/specswarm · 68 tokens

rescue

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

verify

research

criar-skill

research

station

delegate