research

research is a command for Claude Code from yuting0624/antigravity-for-claude-code. It costs 34 tokens per session (592 once invoked), scanned A, original, MIT.

A command for carrying out multi-source web research with a search worker and a separate verification and writing process. It asks for source URLs and dates, then checks important claims before combining the findings.

In plain words
What is it for?
Use it to investigate a topic that needs several sources, verified evidence, and citations. If no topic is supplied, it asks what should be researched.
Why use it?
It reduces the risk of treating unsourced or outdated information as fact. It also breaks a broad research question into smaller questions that can be checked separately.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the antigravity plugin — 2 skills, 11 commands, 1 agent, 2 hooks shipped together

Good fit Use it to investigate a topic that needs several sources, verified evidence, and citations. If no topic is supplied, it asks what should be researched.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yuting0624/antigravity-for-claude-code/research
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.

Clone the repo
git clone --depth 1 https://github.com/yuting0624/antigravity-for-claude-code

Made for: Claude Code.

Or install antigravity, the plugin that ships this one along with the rest of its 2 skills, 11 commands, 1 agent, 2 hooks.

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

agentmods badge for research

README.md
[![agentmods](https://agentmods.dev/badge/commands/yuting0624/antigravity-for-claude-code/research/github.svg)](https://agentmods.dev/commands/yuting0624/antigravity-for-claude-code/research)
Your own site
<a href="https://agentmods.dev/commands/yuting0624/antigravity-for-claude-code/research"><img src="https://agentmods.dev/badge/commands/yuting0624/antigravity-for-claude-code/research/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for research

Your own site · 80×15
<a href="https://agentmods.dev/commands/yuting0624/antigravity-for-claude-code/research"><img src="https://agentmods.dev/badge/commands/yuting0624/antigravity-for-claude-code/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 592 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00034 $0.00592
Opus 5.5 $0.00014 $0.00237
Sonnet 5.5 $0.00007 $0.00118
Haiku 4.5 $0.00003 $0.00059

Measured 1mo ago against content hash 887f52bbe8e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

commands/research.md · 26 lines

What it actually says

Run a multi-source research pass on the topic below, following the antigravity skill's Deep-research recipe and Verification gates. Antigravity (agy / Gemini) is the cheap, grounded search worker; you (Claude) own the plan, the verification, and the synthesis. agy's print-mode citations are coarse (often domain-level) and it can present parametric "knowledge" as a sourced fact — so never ship its citations unchecked.

Topic: $ARGUMENTS

If the topic is empty, ask the user what to research (AskUserQuestion) before starting.

Do this:

  1. Plan (you). Break the topic into 3–6 sub-questions and list the load-bearing claims that must be verified. You own scope and final synthesis.
  2. Fan-out fetch (agy, cheap, one call per sub-question). Web search — and, since agy 1.1.28, any URL read — needs --yolo (or a read_url(<target>) allow-rule) in headless mode; force compact output so bulky pages stay on Gemini's side, not yours: agy-delegate --tier flash --yolo "Web-search <sub-question>. Return 5–8 bullet findings, each with the exact source URL and publication date. Output ONLY findings + URLs + dates."
  3. Deepen on each load-bearing claim (agy). Name the URL and have agy quote the supporting sentence(s), turning domain-level citations into verifiable quotes: agy-delegate --tier pro --yolo "Open <URL> and quote the exact sentence(s) supporting: '<claim>'. If the page does not support it, reply NOT SUPPORTED."
  4. Adversarially verify (you). Corroborate each key claim across ≥2 independent domains; treat any single / vague / domain-only citation as unverified; sanity-check dates; watch for Gemini parametric knowledge posing as a sourced fact.
  5. Synthesize (you). Write a cited report from verified findings only; explicitly mark anything uncorroborated as "unverified".

Keep your own context lean — ingest agy's bullet digests, not the raw pages (that's where the cost savings come from). --print does one agentic pass per call, so re-dispatch follow-up agy calls to close gaps rather than expecting it to auto-iterate. In an interactive session a long fetch can be backgrounded with agy-job; when you are headless (claude -p), delegate synchronously.

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. 1mo ago Changed 887f52bbe8e3
  2. 1mo ago First seen · 26 lines · 34 tokens per session scan A 6810e828f42c

Subscribe to this mod's changes

research is a command published in the GitHub repository yuting0624/antigravity-for-claude-code (416 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 592 once invoked, about $0.0001 per session on Opus 5.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.