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 markfulton/claude-antigravity-agents --skill antigravity-agentsgit clone --depth 1 https://github.com/markfulton/claude-antigravity-agentsWrote 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/markfulton/claude-antigravity-agents/antigravity-agents)<a href="https://agentmods.dev/skills/markfulton/claude-antigravity-agents/antigravity-agents"><img src="https://agentmods.dev/badge/skills/markfulton/claude-antigravity-agents/antigravity-agents/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/markfulton/claude-antigravity-agents/antigravity-agents"><img src="https://agentmods.dev/badge/skills/markfulton/claude-antigravity-agents/antigravity-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 84 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00163 | $0.02012 |
| Opus 5 | $0.00081 | $0.01006 |
| Sonnet 5 | $0.00033 | $0.00402 |
| Haiku 4.5 | $0.00016 | $0.00201 |
Grade A, and why
antigravity-agents 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 10d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity CLI Sub-Agents
Google Antigravity CLI (agy) is an autonomous terminal coding agent (Gemini and other models) that can read a repo, edit files, and run commands. This skill uses its non-interactive print mode to run delegated jobs: you write a self-contained task prompt, launch agy -p in the background, keep doing your own work, then collect and verify the result.
Treat an agy job like a contractor you briefed over email: it only knows what's in the prompt and the directory you point it at, and its work is unverified until you check it.
Resolving the binary
After install, agy is normally on your PATH. If a tool-spawned shell can't find it (some shells don't inherit a freshly updated PATH), fall back to the full path:
- Windows:
%LOCALAPPDATA%\agy\bin\agy.exe(in Bash-style shells:"$LOCALAPPDATA/agy/bin/agy.exe") - macOS / Linux: check
which agy
Critical: always close stdin. agy blocks forever (0% CPU, no output, even in print mode) when stdin is an open pipe, which is exactly what non-interactive tool shells give it. Launch jobs with </dev/null appended (POSIX shells), or from PowerShell via cmd /c '... < NUL'. A "stalled" job with an empty log almost always means stdin was left open — kill it and relaunch with stdin closed.
Preflight (once per session)
Before the first job of a session, verify auth with a cheap probe:
agy -p "Reply with exactly: OK" --print-timeout 60s </dev/null
- Replies
OK→ authenticated, proceed. - Prints a sign-in URL or errors about credentials → stop and tell the user to run
agyonce in their own terminal to complete the Google sign-in (it's a browser OAuth flow you cannot do for them). Don't retry until they confirm. - Hangs with no output → you forgot
</dev/null.
Conflict rule — the one thing that must not go wrong
An agy job and your own edits must never touch the same working tree at the same time. Decide the isolation level before launching:
| Job type | Examples | Isolation |
|---|---|---|
| Read-only | code review, architecture analysis, security audit, research, "explain this codebase", doc summarization | Safe to run concurrently in the same repo. Add --sandbox and say "do not modify any files" in the prompt. |
| Write, different repo | fix a bug in repo B while you work in repo A | Safe concurrently. Launch from repo B's root. |
| Write, same repo | refactor, implement feature, fix tests | Never concurrent with your own edits. Either (a) create a git worktree on a new branch and point the job there, or (b) run it sequentially while you do no edits, then review the diff. |
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.
- 10d ago First seen · 98 lines · 163 tokens per session scan A 49bb3df49d50
antigravity-agents is a skill published in the GitHub repository markfulton/claude-antigravity-agents (120 stars, last pushed 1mo ago), licensed MIT. It adds 163 tokens to every session and 2,012 once invoked, about $0.0008 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 skills, from other repositories
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
security-engineer
Security-first auditing of AI-generated code — Level 1 quick checks during /toh-dev and /toh-test (hardcoded secrets, dangerous code execution, obvious injection vectors) and Level 2 full audits for /toh-protect (SQL/XSS/command injection, auth and authorization flaws, configuration and dependency risks) with…
ui-first-builder
Creates production-ready UI immediately from any description. Generates complete pages, components, and realistic mock data in FIRST response. Uses Next.js 16 + Tailwind + shadcn/ui. Never asks questions - infers everything from context. Triggers: UI creation, page building, component generation, build interface…
memory-system
Tiered, low-token project memory protocol for .toh/memory/ — 7 files across 3 tiers (Tier 1 active.md + summary.md always read, 800 tokens; Tier 2 architecture/components for build work and changelog for debug work; Tier 3 decisions/agents-log only on demand). Auto-saves after task completion with zero user effort…
fabrik-implement
Use when operating as the Fabrik Implement stage agent. This skill guides the implementation of a planned feature, following the task checklist to produce committed, tested, pushed code on a feature branch.
clarify
Finds the vague and missing parts of an existing feature specification and fixes them by asking up to five targeted questions, one at a time, writing each answer back into the spec as it is answered. Follows GitHub Spec Kit's clarify workflow. Use this when someone wants to review, tighten, sharpen, sanity-check, poke…