Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MarcosNahuel/antigravity-plugin-cc/plugin install antigravityWrote 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/deep-research)<a href="https://agentmods.dev/commands/marcosnahuel/antigravity-plugin-cc/deep-research"><img src="https://agentmods.dev/badge/commands/marcosnahuel/antigravity-plugin-cc/deep-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.00149 | $0.02381 |
| Opus 5 | $0.00075 | $0.01190 |
| Sonnet 5 | $0.00030 | $0.00476 |
| Haiku 4.5 | $0.00015 | $0.00238 |
Grade A, and why
deep-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep research command. Does not replace /agy:research (that one is a fast single-shot lookup) —
this one drives a multi-round loop through the deep-research-agy Workflow: agy browses several
angles one at a time per round (never in parallel — see Notes), Claude judges coverage and
convergence between rounds, a red-team pass challenges the central/single-source claims, and only then
does synthesis produce the final report.
Raw user request: $ARGUMENTS
Step 1 — Parse + preflight (ONE Bash call)
-
--depth L|H(defaultL).Hruns up to 4 rounds instead of 2, red-teams up to 10 claims instead of 5, and allows longer per-angle timeouts (4m vs 3m) — reserve it for topics that need real convergence (contradictory sources, a recommendation that must survive red-teaming), not quick lookups. -
--backgroundruns the Workflow withrun_in_background: trueand implies--yes(you can't approve a plan you won't be watching). -
--yesskips the plan gate (Step 3) and goes straight to Step 4. -
--engines agy|mixed(defaultagy).mixedis currently accepted but behaves identically toagy— there is no second browsing engine wired in yet. If the user asks whatmixeddoes, say this plainly; don't imply real engine diversity that doesn't exist. -
Strip all flags above from
$ARGUMENTS; what remains, trimmed, is<topic>. If empty, ask once: "What should I deep-research?" and stop. -
Build
SLUGfrom<topic>(lowercase, non-alphanumeric →-, collapse repeats, trim to 60 chars) andDATE= today, ISOYYYY-MM-DD. -
WRITE_FILE= absolute path todocs/agy/research/<DATE>-<SLUG>.md.DEEP_DIR= absolute path todocs/agy/research/.deep/<DATE>-<SLUG>. -
One Bash call does the preflight + scaffolding together — agy presence check, then both
mkdir -p:mkdir -p "docs/agy/research/.deep/<DATE>-<SLUG>" command -v agy >/dev/null 2>&1 && agy --version || echo "AGY_MISSING"If the output is
AGY_MISSING, tell the user to run/agy:setupfirst and stop — don't launch a multi-round Workflow (several minutes, several agy calls) against a broken/missingagy.
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.
- 7d ago First seen · 146 lines · 149 tokens per session scan A d12a6e4d82e3
deep-research is a command published in the GitHub repository MarcosNahuel/antigravity-plugin-cc (27 stars, last pushed 22d ago), licensed MIT. It adds 149 tokens to every session and 2,381 once invoked, about $0.0007 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-imagegen
Generate or edit an image via a Gemini (agy) session — Gemini's generateimage tool does what Claude cannot.
deep
A command for researching a topic from seven perspectives, including product strategy, user experience, technology, practice, academic work, history, and online discussion. It combines the findings into a web report, Markdown document, and Notion page.
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.