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/airvalona/antigravity-like-claude-code/initnpx skills add airvalona/antigravity-like-claude-code --skill initgit clone --depth 1 https://github.com/airvalona/antigravity-like-claude-codeWrote 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/airvalona/antigravity-like-claude-code/init)<a href="https://agentmods.dev/skills/airvalona/antigravity-like-claude-code/init"><img src="https://agentmods.dev/badge/skills/airvalona/antigravity-like-claude-code/init.svg" alt="Measured on agentmods" 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.00068 | $0.00738 |
| Opus 5 | $0.00034 | $0.00369 |
| Sonnet 5 | $0.00014 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
init 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init — Project Memory Initializer
Port of Claude Code's /init command. Antigravity CLI has no native command that
auto-generates project memory, so this skill fills that gap by producing an
AGENTS.md file (Antigravity's equivalent of CLAUDE.md).
When to run
- The user explicitly asks to
/init, "initialize this project", or "generate project memory". - No
AGENTS.mdexists in the project root and the user is starting real work.
Steps
-
Check for an existing
AGENTS.mdin the project root.- If it exists, read it first and treat this as an update, not an overwrite. Preserve
any manually-added sections (look for a
<!-- manual -->marker) verbatim.
- If it exists, read it first and treat this as an update, not an overwrite. Preserve
any manually-added sections (look for a
-
Inventory the project
- Detect the language(s) and framework(s) from manifest files (
package.json,pyproject.toml,Cargo.toml,go.mod,requirements.txt, etc.). - List the top 2 levels of the directory tree, ignoring
node_modules,.git,dist,build,.venv, and other generated/vendor directories. - Identify entry points (main files, index files, CLI entry scripts).
- Detect the language(s) and framework(s) from manifest files (
-
Extract commands
- Find and record the exact commands for: install, build, run, test, lint, and format.
Pull these from
package.jsonscripts,Makefiletargets,pyproject.toml, CI config files (.github/workflows/*.yml), or README instructions — in that priority order. Never guess a command; if none is found, state that explicitly rather than inventing one.
- Find and record the exact commands for: install, build, run, test, lint, and format.
Pull these from
-
Infer conventions
- Skim a handful of representative source files to note: naming conventions,
import style, error-handling patterns, test file location/naming, and any
linter/formatter config (
.eslintrc,ruff.toml,.prettierrc, etc.). - Do not invent conventions not actually observed in the code.
- Skim a handful of representative source files to note: naming conventions,
import style, error-handling patterns, test file location/naming, and any
linter/formatter config (
-
Write
AGENTS.mdwith this structure:
# Project: <name>
## Overview
<1-3 sentence description inferred from README/package metadata>
## Stack
<languages, frameworks, key dependencies>
## Structure
<top-level directory map with one-line purpose per folder>
## Commands
- Install: `<command>`
- Build: `<command>`
- Test: `<command>`
- Lint: `<command>`
- Run: `<command>`
## Conventions
<observed naming, structure, and style conventions>
## Notes
<anything unusual an agent should know before editing this codebase>
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.
- 5d ago First seen · 77 lines · 68 tokens per session scan A 70b60153c714
init is a skill published in the GitHub repository airvalona/antigravity-like-claude-code (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 738 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…