Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add victalejo/opencode-plugin-cc/plugin install opencodeWrote 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/commands/victalejo/opencode-plugin-cc/rescue)<a href="https://agentmods.dev/commands/victalejo/opencode-plugin-cc/rescue"><img src="https://agentmods.dev/badge/commands/victalejo/opencode-plugin-cc/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/commands/victalejo/opencode-plugin-cc/rescue"><img src="https://agentmods.dev/badge/commands/victalejo/opencode-plugin-cc/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.00020 | $0.00960 |
| Opus 5.5 | $0.00008 | $0.00384 |
| Sonnet 5.5 | $0.00004 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
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 1mo 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.
This is a copy
88% identical to rescue — 40 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Invoke the opencode:rescue subagent via the Agent tool (subagent_type: "opencode:rescue"), forwarding the raw user request as the prompt.
opencode:rescue is a subagent, not a skill — do not call Skill(opencode: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 opencode's output verbatim.
Raw user request: $ARGUMENTS
Execution mode:
- If the request includes
--background, run theopencode:rescuesubagent in the background. - If the request includes
--wait, run theopencode:rescuesubagent in the foreground. - If neither flag is present, default to foreground.
--backgroundand--waitare execution flags for Claude Code. Do not forward them totask, and do not treat them as part of the natural-language task text.--modelis a runtime-selection flag. Preserve it for the forwardedtaskcall, but do not treat it as part of the natural-language task text.--contextis a value-taking flag whose value is a comma-separated list of file paths relative to the workspace. Preserve it (and its value) for the forwardedtaskcall, but do not treat it 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, useAskUserQuestionexactly once to ask whether to continue the current opencode session or start a new one. - The two choices must be:
Continue current opencode sessionStart 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
--resumebefore routing to the subagent. - If the user chooses a new session, add
--freshbefore 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
Bashcall to invokenode "${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. - Pass
--model <value>whenever the user mentions any model name, even colloquial (e.g. "minimax m3", "gpt-4o", "opus"). The companion resolves the name to the correctprovider/modelID automatically. Do not investigate models yourself. Leave--modelunset only when the user does not mention any model at all. - Leave
--resumeand--freshin the forwarded request. The subagent handles that routing when it builds thetaskcommand. - 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.
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.
- 1mo ago First seen · 50 lines · 20 tokens per session scan A 65a7ef3c2a43
rescue is a command published in the GitHub repository victalejo/opencode-plugin-cc (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 960 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to rescue, differing in 40 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.