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 skills add amirkiarafiei/subagent-cli-skills --skill antigravity-cligit clone --depth 1 https://github.com/amirkiarafiei/subagent-cli-skillsWrote 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/skills/amirkiarafiei/subagent-cli-skills/antigravity-cli)<a href="https://agentmods.dev/skills/amirkiarafiei/subagent-cli-skills/antigravity-cli"><img src="https://agentmods.dev/badge/skills/amirkiarafiei/subagent-cli-skills/antigravity-cli/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.
<a href="https://agentmods.dev/skills/amirkiarafiei/subagent-cli-skills/antigravity-cli"><img src="https://agentmods.dev/badge/skills/amirkiarafiei/subagent-cli-skills/antigravity-cli.svg" alt="Reviewed on agentmods" width="80" 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.00084 | $0.02394 |
| Opus 5 | $0.00042 | $0.01197 |
| Sonnet 5 | $0.00017 | $0.00479 |
| Haiku 4.5 | $0.00008 | $0.00239 |
Grade A, and why
antigravity-cli 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 9d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity CLI (subagent/task delegation)
Use Antigravity CLI to run a separate long-horizon pass over the repo: multi-step implementation, broad refactors, batch file writes, or deep exploration—similar to handing a task to a subagent. You stay orchestrator: smaller prompts, less context burn, often lower spend than doing the same work entirely in-session.
When to use Antigravity CLI
- Large or multi-step work: several files, phases, or checkpoints (feature slice, migration, test suite, docs sweep).
- Heavy code generation or editing: Antigravity drives automated tool use while you summarize outcomes and merge.
- Read-only review passes:
--mode plancannot edit by construction, which makes it the right mode for audits, reviews, and "explain how this works" work. - Powerful Web Search: Delegate deep research or API documentation searches to Antigravity to leverage its integrated web search grounding.
- Fresh tool stack: Native Google search grounding, MCP tools, sandbox protection, and other Antigravity-only capabilities.
- User explicitly asks for Antigravity or "use Antigravity CLI for this."
When not to use
- Small / single-step tasks answerable with one or two edits or a short explanation.
- Tight feedback loops where the user wants rapid back-and-forth refinement in one thread.
- Secrets or policy-sensitive flows—avoid piping credentials; redact before delegating.
- Already-loaded context where duplicating the whole plan adds no value—handle locally.
- Low ROI (Return on Investment): If the task requires high precision over a single line or if the time to compose the Handoff Table exceeds the time to simply edit the file locally. Delegation should only be used when the "mental offloading" outweighs the "handoff overhead."
Delegation and context (critical)
Isolated subagent context saves tokens but splits the story: Antigravity does not see the main session's full thread. Poor handoffs cause misread subtasks, conflicting assumptions (stack, style, APIs), and wasted edits.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 126 lines · 84 tokens per session scan A c6b9f160943f
antigravity-cli is a skill published in the GitHub repository amirkiarafiei/subagent-cli-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 2,394 once invoked, about $0.0004 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-31.
Other skills, from other repositories
log-work
Log the work segment that you did after the last work log until now in a.
static
Stash is your personal home for agent work. Everything you create is scoped to your account — it is yours alone, with nothing to pick or set up first. Your Stash has three primary surfaces.
File Manager
Manage files and folders on the computer.
calendar_manager
Manage Google Calendar — create, list, update, delete events with recurring & reminders.
cleanup
Find duplicates, dead links and untagged items in a saved library and propose what to do about each.
parallel
Use when two or more pieces of work are genuinely independent — disjoint files, no shared state, no ordering edge — and should fan out across subagents, then be gathered and reconciled under a combined test suite. Decides WHAT can run concurrently; NOT the isolation it runs in (that is worktrees), NOT the per-unit TDD…