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/marcosnahuel/antigravity-plugin-cc/researchgit clone --depth 1 https://github.com/MarcosNahuel/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/marcosnahuel/antigravity-plugin-cc/research)<a href="https://agentmods.dev/commands/marcosnahuel/antigravity-plugin-cc/research"><img src="https://agentmods.dev/badge/commands/marcosnahuel/antigravity-plugin-cc/research.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.1 | $0.00063 | $0.00629 |
| Opus 5 | $0.00032 | $0.00315 |
| Sonnet 5 | $0.00013 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
research 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 6d 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.
What it actually says
Route this to the antigravity:agy-rescue subagent in MODE: research.
Raw user request: $ARGUMENTS
Routing rules:
- If the request contains
--background, invoke the subagent withrun_in_background: true. Research athighintensity can take 15–20min — background is the sensible default for that case but only when the user explicitly opted in. Strip the flag from the topic. - Parse
--intensity <low|medium|high>from the user text. Default tomediumif missing or invalid. - Strip the routing flags (
--background,--intensity) from the user text. What remains IS the topic. Trim whitespace. - Build a slug from the topic: lowercase, replace non-alphanumeric with
-, collapse repeated-, trim to 60 chars. - Compute today's date in
YYYY-MM-DD(ISO, local time). - Compute
WRITE_FILE=docs/agy/research/<YYYY-MM-DD>-<slug>.md(relative to the current working directory). - Before invoking the subagent, ensure the directory exists with one
Bashcall:
mkdir -p docs/agy/research
Pass this header block to the subagent followed by the topic:
MODE: research
INTENSITY: <low|medium|high>
MODEL:
RESUME: false
WRITE_FILE: docs/agy/research/<date>-<slug>.md
USER_TEXT:
<topic>
Note:
--modelwas rejected byagy1.0.0/1.0.1 but is accepted again in agy 1.0.5+. This plugin defaults to omitting it, soagypicks the model from its own settings; intensity controls the timeout and prompt template only.
Operating rules:
- The subagent wraps the topic in the intensity template, invokes agy with the right timeout (
low=3m,medium=8m,high=20m), writes the result toWRITE_FILE, and returns:- The saved file path.
- The first ~30 lines of agy's output (TL;DR / Executive summary).
- Present that to the user as-is. Do not paraphrase.
- If the user did not provide a topic, ask once: "What topic would you like to research?"
- If agy reports it is missing or unauthenticated, 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.
- 6d ago First seen · 49 lines · 63 tokens per session scan A 97522b6bba48
research is a command published in the GitHub repository MarcosNahuel/antigravity-plugin-cc (26 stars, last pushed 20d ago), licensed MIT. It adds 63 tokens to every session and 629 once invoked, about $0.0003 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
gemini-swarm
Swarm a task across parallel Gemini (agy) sessions with automatic decomposition and model routing.
gemini-imagegen
Generate or edit an image via a Gemini (agy) session — Gemini's generateimage tool does what Claude cannot.
agy-debug
Send an error/stack trace plus the relevant file(s) to Antigravity (agy) for root-cause analysis.
agy-review
Send the current change set to Antigravity (agy) for a senior-reviewer code review.
agy-panel
Ask Antigravity (agy) the same question across several distinct models and compare their answers side by side.
agy
Consult Google's Antigravity CLI (agy) and relay its answer.