result

A command that displays the final output from a completed Gemini job. A job is a task running now or in the background.

In plain words
What is it for?
Use it to read the result of a specific completed job, or the latest finished job in the current session.
Why use it?
It lets you retrieve a review or other delegated task after the work has finished.

Command

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.

agentmods
npx agentmods add commands/arcobaleno64/agy-plugin-cc/result
Clone the repo
git clone --depth 1 https://github.com/arcobaleno64/agy-plugin-cc
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 653 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00653
Opus 5 $0.00006 $0.00327
Sonnet 5 $0.00003 $0.00131
Haiku 4.5 $0.00001 $0.00065

Measured yesterday against content hash 1c39b7acb399, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/gemini/commands/result.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

!node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" status

The user's raw arguments, as text and nothing else: $ARGUMENTS

Those arguments must never reach a shell

The listing above ran before you saw it, with no arguments, on purpose. $ARGUMENTS is substituted into this file as text, so a shell receiving it would evaluate whatever it contains — $(…), backticks, ;, |. Measured on the sibling command: $(echo INJECTED) was executed and its output passed on as the job id.

To fetch a result, build the command from these fixed pieces only:

  • result plus a job id copied character-for-character from the listing above. Job ids are lowercase letters, digits and hyphens, e.g. review-msqu22ju-9c2f32c12b.
  • The literal flag --all, added only because the argument text asked for a job from another session — never copied from that text.

If the user named nothing, run result with no id: the companion returns the most recent finished job of this session.

If the user named something that does not appear in the listing, and they did not ask for --all, say it was not found in this session and stop. Do not pass their text to the companion to find out. With --all, re-run the listing as status --all first, then look again.

Scope

By default result resolves only jobs from the current Claude session, matching /gemini:status — never a job tagged to another session. When no session id is present (running the companion outside Claude Code), only session-agnostic untagged jobs are in scope. --all is what crosses that boundary, deliberately.

Presenting the result

Present the full command output. Do not summarize or condense it. Preserve:

  • Job ID and status
  • The complete result payload: verdict, summary, findings, details, artifacts, next steps
  • File paths and line numbers exactly as reported
  • Any error messages or parse errors
  • Follow-up commands such as /gemini:status <id>, /gemini:review --wait, and /gemini:adversarial-review --wait
  • The session/conversation ID and its resume command, which are engine-specific: gemini jobs show Gemini session ID + gemini --resume <id>; AGY jobs show AGY conversation ID + agy --conversation <id>

Read the full file on GitHub · 61 lines

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. yesterday First seen · 61 lines · 13 tokens per session scan A 1c39b7acb399

Subscribe to this mod's changes

result is a command published in the GitHub repository arcobaleno64/agy-plugin-cc (10 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 653 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.