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 yuting0624/antigravity-for-claude-code/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/skills/yuting0624/antigravity-for-claude-code/migrate-to-antigravity)<a href="https://agentmods.dev/skills/yuting0624/antigravity-for-claude-code/migrate-to-antigravity"><img src="https://agentmods.dev/badge/skills/yuting0624/antigravity-for-claude-code/migrate-to-antigravity/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/yuting0624/antigravity-for-claude-code/migrate-to-antigravity"><img src="https://agentmods.dev/badge/skills/yuting0624/antigravity-for-claude-code/migrate-to-antigravity.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.00123 | $0.02012 |
| Opus 5 | $0.00062 | $0.01006 |
| Sonnet 5 | $0.00025 | $0.00402 |
| Haiku 4.5 | $0.00012 | $0.00201 |
Grade B, and why
migrate-to-antigravity scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| `~/.gemini/config/` — `mcp_config.json`, `skills/`, `plugins/`, `skills.json`, `projects/` | CLI **and** both desktop apps | How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating Claude Code → Antigravity CLI
Run agy-migrate (dry-run) → read the report → agy-migrate --apply.
agy-migrate --uninstall --apply reverses everything.
The tool treats the Claude Code config dir as read-only. The single exception is
an AGENTS.md symlink placed beside an existing CLAUDE.md, and only under
--include-repos.
Where the two products keep things
Claude Code — ~/.claude/ plus ~/.claude.json, relocatable together via
CLAUDE_CONFIG_DIR. Two things surprise people: there is usually no
~/.claude/CLAUDE.md, and auto-memory is per project, under
~/.claude/projects/<encoded-cwd>/memory/. The encoding maps /, _ and . all to
-, so it can only be matched forward (re-encode a known path), never decoded.
Claude Desktop / Cowork is a separate universe. It has its own
~/Library/Application Support/Claude/claude_desktop_config.json (MCP) and
Claude Extensions/ (.mcpb), and its Cowork skills are server-synced into
local-agent-mode-sessions/skills-plugin/, so no local original exists to migrate.
Only claude_desktop_config.json's mcpServers is portable, and the tool picks it up.
The bundled claude-code/<version>/claude.app inside the desktop app is the ordinary
CLI and does read ~/.claude.
Antigravity — rooted at ~/.gemini/, not ~/.antigravity:
| Path | Shared by |
|---|---|
~/.gemini/config/ — mcp_config.json, skills/, plugins/, skills.json, projects/ |
CLI and both desktop apps |
~/.gemini/antigravity-cli/settings.json |
agy only |
~/.gemini/{antigravity-cli,antigravity,antigravity-ide}/ — conversations, brain, knowledge |
each surface separately |
So customization is shared across surfaces; session state is not.
What moves, and how
| Asset | Mechanism | Notes |
|---|---|---|
| User skills | live — skills.json entry pointing at ~/.claude/skills |
no copy; edits show up on both sides |
| Installed plugins | native agy plugin import claude, run in a staging HOME |
output is then repaired (below) |
CLAUDE.md |
symlink AGENTS.md → CLAUDE.md |
--include-repos; both are plain Markdown |
| Auto-memory | generated rules | global → a plugin's rules/; per-repo → <repo>/.agents/rules/ |
| MCP servers | merged + translated into mcp_config.json |
url/httpUrl → serverUrl, type dropped |
| Trusted projects | trustedWorkspaces |
the one clean settings mapping |
| Permissions | proposal only by default | see the warning below |
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 · 141 lines · 123 tokens per session scan B e2679e1233f0
migrate-to-antigravity is a skill published in the GitHub repository yuting0624/antigravity-for-claude-code (321 stars, last pushed 3d ago), licensed MIT. It adds 123 tokens to every session and 2,012 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
build-user-persona
Build evidence-backed user personas from research inputs. Creates structured persona documents grounded in evidence, with each attribute clearly labeled as research-validated or inferred. Use this skill when you need personas for an FR, strategy doc, or design brief. Trigger on: "build a persona", "create user…
competitive-analysis
Structure a competitive landscape analysis — player profiles, capability comparison matrix, whitespace opportunities, and strategic implications. Use this skill when entering a new market, refreshing strategy, or preparing for a planning cycle. Trigger on: "do a competitive analysis", "who are our competitors"…
write-product-strategy
Generate comprehensive product strategy documents aligned with business goals. Use this when defining or updating your product's strategic direction, aligning teams on where to play and how to win, or creating a STRATEGY.md that bridges vision and execution. Triggers include: clarifying product strategy, articulating…
synthesize-user-research
Synthesize raw user research (interview notes, survey results, support tickets, NPS verbatims) into structured insights: themes, pain points, jobs-to-be-done, and research gaps. Use this skill when you need to make sense of qualitative research data before writing a feature request or building personas. Trigger on…
write-feature-request
Guided Feature Request (FR) authoring. Assists the user in writing a high-quality FR by collecting structured inputs (problem, solution, outcomes, requirements), then auto-generates Acceptance Criteria for every requirement. If any AC cannot be written due to missing information, the skill identifies the gaps and…
write-okrs
Generate well-structured OKRs from a product strategy. Derives Objectives and Key Results from strategy pillars, challenges vague KRs, distinguishes outputs from outcomes, and links each OKR back to the strategy pillar it serves. Trigger on: "write our OKRs", "help me set OKRs for this quarter", "turn this strategy…