ag-status

A command that checks whether the Antigravity worker, which uses the agy or Gemini command-line tool, is installed and configured.

In plain words
What is it for?
Use it to check Antigravity setup and, if everything is ready, optionally run a small test request.
Why use it?
It quickly shows whether this worker is ready without revealing secret values.

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/rbinar/cli-dispatch/ag-status
Clone the repo
git clone --depth 1 https://github.com/rbinar/cli-dispatch
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 140 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.00140
Opus 5 $0.00006 $0.00070
Sonnet 5 $0.00003 $0.00028
Haiku 4.5 $0.00001 $0.00014

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

Security

Grade A, and why

ag-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/cli-dispatch/commands/ag-status.md · 14 lines

What it actually says

!bash "${CLAUDE_PLUGIN_ROOT}/scripts/cli-dispatch-status.sh" --backend antigravity "${CLAUDE_PLUGIN_ROOT}"

The Antigravity status report above already ran — do NOT run it again. Present it as-is and keep it compact. The report never prints a key VALUE, only whether one is set — keep it that way. For all backends use /cli-dispatch:status.

If everything is in place, suggest an optional smoke test (background task): ag-agent -q "Reply with exactly: OK".

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 · 14 lines · 13 tokens per session scan A 4d45907f2f5b

Subscribe to this mod's changes

ag-status is a command published in the GitHub repository rbinar/cli-dispatch (5 stars, last pushed 14d ago), licensed MIT. It adds 13 tokens to every session and 140 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.