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 skills/limeflash/antigravity-plugin-cc/antigravity-clinpx skills add limeflash/antigravity-plugin-cc --skill antigravity-cligit clone --depth 1 https://github.com/limeflash/antigravity-plugin-ccWhat 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.00032 | $0.00727 |
| Opus 5 | $0.00016 | $0.00364 |
| Sonnet 5 | $0.00006 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00073 |
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 yesterday.
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.
This is a copy
100% identical to antigravity-cli — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity CLI runtime
Use this skill only inside the agy subagent.
Primary helper
bash "${CLAUDE_PLUGIN_ROOT}/scripts/agy-run.sh" ask [--model <alias>] "<prompt>" [agy-flags...]
The wrapper:
- Locates
agyinPATH,~/.local/bin,/opt/antigravity/bin, or/usr/local/bin. - Verifies auth (system keyring OAuth or
ANTIGRAVITY_API_KEY). - Runs
agy -p "<prompt>"non-interactively. - If
--model <alias>is supplied before the prompt, resolves the alias and applies it for the duration of the call (atomic patch of~/.gemini/antigravity-cli/settings.jsonunder a lockfile, restored on exit). - Forwards any extra arguments after the prompt straight to
agy— so… ask "<prompt>" --sandboxbecomesagy -p "<prompt>" --sandbox.
Rules of engagement
One wrapper call per task. The subagent is a forwarder, not an orchestrator —
keep the user's task text intact and let agy do the work.
Strip flags that belong to the parent slash command (--background) before
forwarding. Pass --model <alias> to the wrapper (not to agy directly).
Pass agy-native flags through after the prompt argument.
Model aliases (consumed by the wrapper)
flash-low, flash-medium (flash-med), flash (flash-high),
pro-low, pro (pro-high), sonnet (claude-sonnet),
opus (claude-opus), gpt-oss (gpt-oss-120b). Canonical TUI strings
are also accepted verbatim (e.g. "Claude Opus 4.6 (Thinking)").
Run bash "${CLAUDE_PLUGIN_ROOT}/scripts/agy-run.sh" help for the
authoritative list.
agy-native flags worth knowing
Run agy --help for the full list. Useful ones that go after the
prompt argument:
--sandbox— extra-restrictive execution; only when the user asked for it.--print-timeout 10m— extend the default 5min print timeout.--add-dir <path>— add a directory to the workspace (repeatable).
What this skill does NOT do
- Does not install or authenticate
agy. That is/agy:setup's job. - Does not retry, summarize, or post-process
agy's output. - Does not read files, run
git, or make HTTP calls outside the wrapper.
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.
- yesterday First seen · 73 lines · 32 tokens per session scan A 1bcf818b98d7
antigravity-cli is a skill published in the GitHub repository limeflash/antigravity-plugin-cc (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 727 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to antigravity-cli, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…