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 LovelaceLoom/gemini-plugin-cc --skill gemini-result-handlinggit clone --depth 1 https://github.com/LovelaceLoom/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/lovelaceloom/gemini-plugin-cc/gemini-result-handling)<a href="https://agentmods.dev/skills/lovelaceloom/gemini-plugin-cc/gemini-result-handling"><img src="https://agentmods.dev/badge/skills/lovelaceloom/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/lovelaceloom/gemini-plugin-cc/gemini-result-handling"><img src="https://agentmods.dev/badge/skills/lovelaceloom/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.00017 | $0.00578 |
| Opus 5 | $0.00009 | $0.00289 |
| Sonnet 5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presenting Gemini output
Use this skill from the main Claude Code thread when surfacing output from a Gemini companion command (review, adversarial-review, task, result).
Default rule: verbatim
Return Gemini's stdout to the user verbatim. Do not paraphrase, summarize, re-style, or "improve" the output. The user invoked Gemini deliberately to get a second opinion in Gemini's voice — sanitizing it through Claude defeats the purpose.
When to add framing
Wrap Gemini's output in a short header only when:
- It came from
/gemini:rescueand the user might not realize a delegation just happened. A one-line "Gemini's response:" header is fine. - It came from
/gemini:reviewand arrived inside anAskUserQuestionflow where the user picked "background". A one-line follow-up "Gemini review (job ) completed — output above" is fine.
When NOT to add framing
/gemini:ask— the user asked a direct question, just return the answer./gemini:status— the companion already renders a Markdown table; pass it through./gemini:result— the output is already structured. Don't re-format.
Auth-error hints
If the companion's stderr contains a [hint: ...] line, surface that hint to the user and suggest /gemini:setup. Do not try to recover yourself.
JSON review output
If /gemini:review --json was used, the companion strips Gemini's wrapper ({session_id, response, stats}), removes markdown code fences, and emits clean JSON. The shape is checked against schemas/review-output.schema.json at the top level (verdict / summary / findings / next_steps must be present and verdict must be in the enum); deeper field-level validation is the caller's responsibility. When forwarding it:
- If the user asked for JSON specifically, pass it through unmodified.
- If the user did not ask for JSON, render the JSON into a compact Markdown report grouped by
severity. Preservefile,line_start,line_end, andrecommendationfor each finding. - If the companion's stderr contains
schema mismatch, surface that warning along with the raw output — Gemini may have ignored the schema instruction.
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.
- 12d ago First seen · 41 lines · 17 tokens per session scan A d2c1acaed727
gemini-result-handling is a skill published in the GitHub repository LovelaceLoom/gemini-plugin-cc (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 578 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 skills, from other repositories
multi-perspective-review
Multi-perspective collaborative review of plans or documents. Ten expert viewpoints deliberate in 3 rounds to reach consensus.
review
Run a full code review on current changes or specified files. Runs ruff lint, review-code agent, and security scan in sequence.
plan-task
Structured task planning using Work files. Use for any new feature, bug fix, or project that needs a task breakdown before implementation.
brainstorming
Design and spec before any planning or code. MUST USE before new features, creative work, or any implementation. Explores requirements, proposes approaches, gets design approval, then chains to plan-task.
debug
Analyze errors and apply fixes. Use when you have an error message, traceback, or failing log to diagnose.
release-init
Detect project type and generate a tailored project-level /release skill. Run once per project to set up releasing.