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 madciapka/gemini-claude-plugin/plugin install geminiWrote 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/madciapka/gemini-claude-plugin/rescue-stream)<a href="https://agentmods.dev/commands/madciapka/gemini-claude-plugin/rescue-stream"><img src="https://agentmods.dev/badge/commands/madciapka/gemini-claude-plugin/rescue-stream.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.1 | $0.00013 | $0.00586 |
| Opus 5 | $0.00006 | $0.00293 |
| Sonnet 5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
rescue-stream 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 8d 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
Use this when the Gemini run is long, open-ended, or write-capable and you want Claude to react to interim progress (file edits, tool calls, partial findings) instead of waiting for one final blob.
Use /gemini:rescue (not this command) when you only need Gemini's final answer as a single artifact.
Raw user request: $ARGUMENTS
Operating contract:
- Run a Bash call to launch the streamed background job:
The companion prints a JSON-ish payload (node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" task --stream "$ARGUMENTS"jobId,eventsFile,logFile). - Capture the
jobIdandeventsFilefrom that output. - Tail the job with
node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" tail "$jobId"(run_in_background: true) and read new lines viaBashOutputperiodically. Do not use rawtail -F— it leaks. The companion'stailexits on terminal job status. - Each event line is JSON-line (
stream-json). Commontypevalues includeinit,message,tool_use,error. Treat lines that fail to parse as raw progress text. - The companion's
tailexits on its own when the job iscompleted/failed/cancelled. If it's still running after 30 s with no new lines, surface a stall. - After completion, fetch the final response with:
and return that verbatim, exactly likenode "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" result <jobId>/gemini:rescue.
Argument handling:
- Preserve the user's natural-language task text exactly.
--model,--read-only,--yolo,--sandboxare runtime flags — pass them through.- Do not strip
--stream; the helper requires it. - Default to
--read-onlywhen the user asked for review/diagnosis/research with no explicit request to apply fixes.
Don'ts:
- Do not paraphrase or summarize Gemini's events. Surface them verbatim.
- Do not fall back to
/gemini:rescueif streaming fails — surface the error and stop. - Do not auto-apply fixes from a streamed review. Same rule as
/gemini:rescue.
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.
- 8d ago First seen · 44 lines · 13 tokens per session scan A e3893aababce
rescue-stream is a command published in the GitHub repository madciapka/gemini-claude-plugin (8 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 586 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.