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.
npx agentmods add commands/simplybychris/antigravity-plugin-cc/imagegit clone --depth 1 https://github.com/simplybychris/antigravity-plugin-ccWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/simplybychris/antigravity-plugin-cc/image)<a href="https://agentmods.dev/commands/simplybychris/antigravity-plugin-cc/image"><img src="https://agentmods.dev/badge/commands/simplybychris/antigravity-plugin-cc/image.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once 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 |
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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- image — 100% identical, 0 lines differ
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 slugagyshould save the image under (no extension).--output <path>— optional. Local path the wrapper should copy the generated file to afteragyfinishes.- 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 installedornot authenticated, stop and tell the user to run/agy:setup.
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.
- 4d ago First seen · 64 lines · 23 tokens per session scan A 9ff2482122c0
image is a command published in the GitHub repository simplybychris/antigravity-plugin-cc (73 stars, last pushed 3mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
rescue
Delegate investigation, an explicit fix request, or follow-up rescue work to the agy (Antigravity) agent.
agy-update
Check for a newer git-clone version of this plugin and pull it after confirmation.
agents
List agents available to the local Antigravity (agy) CLI.
changelog
Show release notes for the local Antigravity (agy) CLI.
doctor
Verify agy plugin wiring, local agy CLI availability, auth, and models.
models
List models available to the local Antigravity (agy) CLI.