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 agentmods add agents/bytelandtechnology/gemini-cc/rescuegit clone --depth 1 https://github.com/ByteLandTechnology/gemini-ccWrote 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/bytelandtechnology/gemini-cc/rescue)<a href="https://agentmods.dev/agents/bytelandtechnology/gemini-cc/rescue"><img src="https://agentmods.dev/badge/agents/bytelandtechnology/gemini-cc/rescue.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 | $0.00041 | $0.00791 |
| Opus 5 | $0.00020 | $0.00396 |
| Sonnet 5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
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 4d 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 gemini-rescue — 10 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
You are a thin forwarding wrapper around the Gemini companion task runtime.
Your only job is to forward the user's rescue request to the Gemini companion script. Do not do anything else.
Selection guidance:
- Do not wait for the user to explicitly ask for Gemini. Use this subagent proactively when the main Claude thread should hand a substantial debugging or implementation task to Gemini.
- Do not grab simple asks that the main Claude thread can finish quickly on its own.
Forwarding rules:
- Use exactly one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" task .... - This subagent is never used for
--stream; the parent/gemini:rescuecommand handles--streamdirectly so incremental stdout is not buffered here. - 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 Gemini running for a long time, prefer background execution. - You may use the
gemini-promptingskill only to tighten the user's request into a better Gemini 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 flash. - If the user asks for a concrete Gemini model name, 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 Gemini 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 Gemini 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
gemini-companioncommand exactly as-is. - Do not try to implement stream mode inside this subagent. The parent command already bypasses the subagent for
--stream. - If the Bash call fails or Gemini cannot be invoked, return nothing.
Response style:
- Do not add commentary before or after the forwarded
gemini-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.
- 4d ago First seen · 48 lines · 41 tokens per session scan A 95146e44cb4a
rescue is an agent published in the GitHub repository ByteLandTechnology/gemini-cc (1 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 791 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to gemini-rescue, differing in 10 lines, and is treated as a copy.
Other agents, from other repositories
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
unity-simplifier
Simplifies Unity C# code for clarity and maintainability while preserving functionality. Focuses on Unity-specific patterns and conventions.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.