status

A command that lists active and recent Gemini jobs and their review-gate status.

In plain words
What is it for?
Use it to find job IDs, monitor reviews or tasks, wait for completion, and inspect results available for the repository.
Why use it?
It shows whether delegated work is waiting, running, finished, or needs attention.

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/status
Clone the repo
git clone --depth 1 https://github.com/arcobaleno64/agy-plugin-cc
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 598 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.00015 $0.00598
Opus 5 $0.00008 $0.00299
Sonnet 5 $0.00003 $0.00120
Haiku 4.5 $0.00002 $0.00060

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

Security

Grade A, and why

status 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/status.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 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 block above already ran, before you saw it, and it ran with no arguments on purpose. $ARGUMENTS is substituted into this file as text, so a shell that received it would evaluate whatever it contains — $(…), backticks, ;, |. Measured: /gemini:status $(echo INJECTED) executed the substitution and passed INJECTED on as the job id.

So when you build a command, assemble it only from these fixed pieces:

  • The literal flag --all, --wait, or --timeout-ms <n> — included because the argument text asked for it, never copied from it. <n> must be a value you have checked is entirely digits.
  • A job id copied character-for-character out of the companion output above. Job ids look like review-msqu22ju-9c2f32c12b: lowercase letters, digits and hyphens only. If what the user typed is not present in that output, say so and stop — do not pass their text through to find out.

Never place the argument text, or any fragment of it, into a command. Never pass it as a single quoted string.

Presenting the result

If the user did not name a job:

  • Render the output above as a single Markdown table of this session's runs.
  • Keep it compact. No progress blocks or extra prose outside the table.
  • Preserve the actionable fields: job ID, kind, status, phase, elapsed or duration, summary, and follow-up commands.

If the user named a job that appears in the output above:

  • Present that job's full entry. Do not summarize or condense it.

A status of partial is not a failure. It means the engine was cut off after it had produced text: the output is stored and readable with /gemini:result, but nothing confirmed it is the whole answer. Say so rather than reporting the job as failed, and point at /gemini:result before suggesting a re-run — a re-run is billed from the start.

Read the full file on GitHub · 54 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 · 54 lines · 15 tokens per session scan A dcb18ff625bd

Subscribe to this mod's changes

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