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 skills add spyrae/gemini-plugin-cc --skill gemini-result-handlinggit clone --depth 1 https://github.com/spyrae/gemini-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/skills/spyrae/gemini-plugin-cc/gemini-result-handling)<a href="https://agentmods.dev/skills/spyrae/gemini-plugin-cc/gemini-result-handling"><img src="https://agentmods.dev/badge/skills/spyrae/gemini-plugin-cc/gemini-result-handling/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/skills/spyrae/gemini-plugin-cc/gemini-result-handling"><img src="https://agentmods.dev/badge/skills/spyrae/gemini-plugin-cc/gemini-result-handling.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.00014 | $0.00310 |
| Opus 5.5 | $0.00006 | $0.00124 |
| Sonnet 5.5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
gemini-result-handling 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 2mo 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
Gemini Result Handling
Core rules
-
Show reviews verbatim. Do NOT summarize, rephrase, or add commentary to review output from
/gemini:reviewor/gemini:adversarial-review. Show it exactly as Gemini produced it. -
Do NOT auto-apply fixes after review. When Gemini identifies issues in a review, do NOT automatically start fixing them. Present the findings and wait for the user to decide what to do.
-
Review task output before applying. When
/gemini:rescuereturns code changes, examine them critically. Gemini may:- Use different patterns than the project's conventions
- Miss project-specific constraints
- Introduce dependencies not approved for the project
- Make assumptions about the codebase that don't hold
-
Report failures honestly. If Gemini returns an error or empty output, report that clearly. Do NOT fabricate or guess what Gemini would have said.
-
Background job status. When a background job is running, inform the user of the job ID and how to check status. Do NOT poll or wait silently.
After review
Present findings, then ask: "Would you like me to address any of these findings?"
After rescue/task
Present Gemini's output, then: "Here's what Gemini produced. Should I review and apply these 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.
- 2mo ago First seen · 32 lines · 14 tokens per session scan A d3e6f4d5e58b
gemini-result-handling is a skill published in the GitHub repository spyrae/gemini-plugin-cc (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 310 once invoked, about $0.0001 per session on Opus 5.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.
gemini-result-handling compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gemini-result-handlingspyrae/gemini-plugin-cc | Skill | 2 | 7mo ago | Apache-2.0 | A | 14 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |