ag-sessions

A command that lists saved Antigravity, also called Gemini, worker sessions. It reads basic session status information without opening the full conversation transcript.

In plain words
What is it for?
Use it to review Antigravity sessions, then watch a session for live details or resume it with a follow-up request.
Why use it?
It shows which sessions exist and presents the newest ones first without loading unnecessary data.

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-sessions
Clone the repo
git clone --depth 1 https://github.com/rbinar/cli-dispatch
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 158 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.00011 $0.00158
Opus 5 $0.00005 $0.00079
Sonnet 5 $0.00002 $0.00032
Haiku 4.5 $0.00001 $0.00016

Measured 2d ago against content hash 9fc036460477, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ag-sessions 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 2d 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/cli-dispatch/commands/ag-sessions.md · 15 lines

What it actually says

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

The Antigravity session listing above already ran — do NOT run it again. Present it as-is, newest first; this filtered view has no backend column. Cost-conscious: it reads only meta.json + status.json; transcript.jsonl is NEVER read. For every backend at once use /cli-dispatch:sessions.

To see a session's detail/live status: /cli-dispatch:watch <id>. To send a follow-up (continue the same session): /cli-dispatch:resume <id> <follow-up>.

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. 2d ago First seen · 15 lines · 11 tokens per session scan A 9fc036460477

Subscribe to this mod's changes

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