gemini-result-handling

gemini-result-handling is a skill for Claude Code from spyrae/gemini-plugin-cc. It costs 14 tokens per session (310 once invoked), scanned A, original, Apache-2.0.

Guidance for presenting results from Gemini jobs and reviews to the user.

In plain words
What is it for?
Use it when showing Gemini review or rescue output, reporting job status, deciding whether to apply fixes, and asking what to address next.
Why use it?
It prevents reviews from being silently summarised or changed, and makes failures, background jobs, and suggested fixes explicit.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the g-cc plugin — 3 skills, 7 commands, 1 agent, 3 hooks shipped together

Good fit Use it when showing Gemini review or rescue output, reporting job status, deciding whether to apply fixes, and asking what to address next.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spyrae/gemini-plugin-cc/gemini-result-handling
Install

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.

Any agent
npx skills add spyrae/gemini-plugin-cc --skill gemini-result-handling
Clone the repo
git clone --depth 1 https://github.com/spyrae/gemini-plugin-cc

Made for: Claude Code.

Or install g-cc, the plugin that ships this one along with the rest of its 3 skills, 7 commands, 1 agent, 3 hooks.

Wrote 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.

agentmods badge for gemini-result-handling

README.md
[![agentmods](https://agentmods.dev/badge/skills/spyrae/gemini-plugin-cc/gemini-result-handling/github.svg)](https://agentmods.dev/skills/spyrae/gemini-plugin-cc/gemini-result-handling)
Your own site
<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.

agentmods 80×15 button for gemini-result-handling

Your own site · 80×15
<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>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00310
Opus 5 $0.00007 $0.00155
Sonnet 5 $0.00003 $0.00062
Haiku 4.5 $0.00001 $0.00031

Measured 10d ago against content hash d3e6f4d5e58b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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.

plugins/gemini/skills/gemini-result-handling/SKILL.md · 32 lines

What it actually says

Gemini Result Handling

Core rules

  1. Show reviews verbatim. Do NOT summarize, rephrase, or add commentary to review output from /gemini:review or /gemini:adversarial-review. Show it exactly as Gemini produced it.

  2. 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.

  3. Review task output before applying. When /gemini:rescue returns 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
  4. Report failures honestly. If Gemini returns an error or empty output, report that clearly. Do NOT fabricate or guess what Gemini would have said.

  5. 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?"

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.

  1. 10d ago First seen · 32 lines · 14 tokens per session scan A d3e6f4d5e58b

Subscribe to this mod's changes

gemini-result-handling is a skill published in the GitHub repository spyrae/gemini-plugin-cc (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 310 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens