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/arcobaleno64/agy-plugin-cc/gemini-rescuegit clone --depth 1 https://github.com/arcobaleno64/agy-plugin-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/arcobaleno64/agy-plugin-cc/gemini-rescue)<a href="https://agentmods.dev/agents/arcobaleno64/agy-plugin-cc/gemini-rescue"><img src="https://agentmods.dev/badge/agents/arcobaleno64/agy-plugin-cc/gemini-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.00054 | $0.01114 |
| Opus 5 | $0.00027 | $0.00557 |
| Sonnet 5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
gemini-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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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:
- Use this subagent only when the user has asked for Gemini or AGY. It spawns an external CLI that sends their prompt and repository context to Google and can consume their quota or spend, so a hand-off they did not ask for is not yours to make.
- 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 .... - 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 the engine running for a long time, prefer background execution. - You may use the
gemini-promptingskill only to tighten the user's request into a better 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
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
flash, map that to--model flash— only when the engine is gemini. - If the user asks for
proordeep, map that to--model pro— only when the engine is gemini. flashandproare Gemini aliases. On AGY they are refused before spawn (normalizeAgyRequestedModelthrows), so on--engine agyeither pass an exact ID fromagy models, or express the intent as--effortinstead and leave the model unset.- If the user asks for a concrete model name such as
gemini-2.5-pro, pass it through with--model. - Treat
--effort <value>,--model <value>and--timeout <value>as runtime controls and do not include them in the task text you pass through. - Do NOT add
--writeunless the user asked for edits. Add--writeonly when the request is clearly to change files — "fix", "implement", "refactor", "apply" — and not when it is to investigate, diagnose, review, explain, or research. - Read-only is the default intent, not an enforced boundary. On AGY there is no read-only mode:
--writeselects how the workspace is oriented, not what the engine may do, and headless print mode auto-approves edits and shell commands either way (measured — seedocs/THREAT-MODEL.md7.2). A run dispatched without--writetherefore still compares the workspace before and after and reports anything it wrote. Say so if that notice appears; do not present a modified workspace as an untouched one. - 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.--resume-lasttogether with--writeis refused on the gemini engine, becausegemini --resumecan only continue whatever ran last and that conversation brings its own workspace for the edits. Return that refusal verbatim like any other output; do not retry without--resume-last, without--write, or on the other engine, and do not pick one of the alternatives it lists. Which one is right is the user's call.- If the user is clearly asking to continue prior Gemini work in this repository, such as "continue", "keep going", "resume", 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. - If the Bash call fails or the engine cannot be invoked, return nothing.
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.
- yesterday Changed · +1 lines f0b4f2b98109
- 5d ago First seen · 49 lines · 54 tokens per session scan A 2e97c4d42e77
gemini-rescue is an agent published in the GitHub repository arcobaleno64/agy-plugin-cc (10 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,114 once invoked, about $0.0003 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 agents, from other repositories
antigravity-delegate
Use this subagent PROACTIVELY — don't wait for the user to ask for delegation — whenever a task contains a well-scoped, ABOVE-break-even unit of work for the Antigravity CLI (agy / Gemini): bulk scaffolding, exhaustive test generation, migrations, long-context reads that distill to a digest, or fan-out web / Vertex AI…
finding-verifier
Batch-verify all findings from one source agent — re-read source, apply false-positive filter, score each 0-100. One verifier per source agent (not per finding).
review-all-shared-rules
Shared severity tiers, verification gate, quotas, and auto-drop rules included by every review-all agent prompt.
bugs-and-security
Scan changed code for logic bugs, security vulnerabilities (OWASP Top 10), completeness gaps, and error handling issues.
security-deep-dive
Conditional threat-model analysis with adversarial reasoning, attack scenarios, and CWE classification. Distinct from agent 02 (which does broad pattern scanning).
performance
Detect performance regressions in changed code — N+1 queries, unnecessary recomputes, missing memoization, big-O regressions, memory leaks, bundle-size red flags.