image

A command for asking the Antigravity command-line tool to create an image from a written description.

In plain words
What is it for?
Use it to generate an image, optionally choosing its filename and where the resulting file should be saved.
Why use it?
It handles the command details and can copy the generated image to a local path, so you do not need to manage the image tool yourself.

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/limeflash/antigravity-plugin-cc/image
Clone the repo
git clone --depth 1 https://github.com/limeflash/antigravity-plugin-cc
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 522 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00023 $0.00522
Opus 5 $0.00012 $0.00261
Sonnet 5 $0.00005 $0.00104
Haiku 4.5 $0.00002 $0.00052

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to image — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/agy/commands/image.md · 64 lines

What it actually says

Ask agy to generate an image. The Antigravity CLI ships a native generate_image tool (Imagen under the hood) that triggers automatically when the prompt asks for an image — the wrapper builds the right prompt and extracts the saved file path.

The user's request (treat as opaque — pass through as shell-safe arguments):

$ARGUMENTS

How to invoke

Parse the user's request into three parts:

  • --name <slug> — optional. Filename slug agy should save the image under (no extension).
  • --output <path> — optional. Local path the wrapper should copy the generated file to after agy finishes.
  • The remaining text — the description of what to generate.

Use the Bash tool to run:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/agy-run.sh" image "<description>" [--name <slug>] [--output <path>]

…with the description quoted as one shell argument so characters like ", $, ; cannot break out.

How the wrapper finds the saved path

The wrapper builds a prompt that asks agy to end its reply with a single line:

IMAGE_PATH: <absolute path to the generated image>

This is the primary contract. If agy honors it, the wrapper picks the path up deterministically and (when --output is set) copies the file there. As a fallback, the wrapper also scrapes any absolute *.png/.jpg/.jpeg/.webp path that appears in agy's reply.

If neither is found, the wrapper prints a clear warning so the user knows the file wasn't located. Generated files normally live under ~/.gemini/antigravity-cli/brain/<uuid>/<name>.<ext>.

Notes

  • Return Antigravity's full text response verbatim so the user can see the generated path.
  • If the user did not provide any description, ask what they want to generate.
  • If the wrapper reports agy is not installed or not authenticated, stop and tell the user to run /agy:setup.
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 · 64 lines · 23 tokens per session scan A 9ff2482122c0

Subscribe to this mod's changes

image is a command published in the GitHub repository limeflash/antigravity-plugin-cc (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 522 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to image, differing in 0 lines, and is treated as a copy.