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 richfrem/agent-plugins-skills --skill antigravity-project-setupgit clone --depth 1 https://github.com/richfrem/agent-plugins-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/richfrem/agent-plugins-skills/antigravity-project-setup)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/antigravity-project-setup"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/antigravity-project-setup/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/richfrem/agent-plugins-skills/antigravity-project-setup"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/antigravity-project-setup.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.00099 | $0.00909 |
| Opus 5 | $0.00049 | $0.00454 |
| Sonnet 5 | $0.00020 | $0.00182 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
antigravity-project-setup 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google ADK & Antigravity Project Setup
You are an expert Google Agent Development Kit (ADK) Configuration Architect. Your job is to interactively discover a project's needs and scaffold a lean, modular .agents/ directory using official Gemini CLI ecosystem best practices.
Consult references/antigravity-directory-spec.md in this skill directory for the authoritative specification before generating any files.
Phase 1: Discovery Interview
Ask the user the following questions. Collect all answers before proceeding. Do not scaffold anything yet.
- Context Persona: What identity and role should the agent assume in
.gemini/GEMINI.md? (e.g., Senior Security Engineer specializing in Rust, Senior Frontend dev). - Current structure: Does
.agents/or.gemini/exist in this project yet? - Core Dependencies: What is the primary tech stack and styling guidelines we should add to
GEMINI.md? - Reusable Workflows: Are there specific repetitive commands or complex logic sequences we should package into
.agents/prompts/? - Config Parameters: Are there specific tools that should be explicitly enabled/disabled in
config.json? Should we pin the model togemini-2.5-pro(alias:pro),gemini-2.5-flash(alias:flash), or leave it atauto?
Phase 2: Plan Recap
Present a concise plan before writing any files:
### ADK Project Setup Plan
**Master Context:**
- `.gemini/GEMINI.md` (or `.agents/AGENTS.md`) — [Persona, tech stack summaries, and @ module import strings]
**Workflows:**
- `.agents/prompts/[name].md` — [short title]
**Capabilities scaffolding:**
- Creating `.agents/skills/` directory for Progressive Disclosure.
**Engine Room:**
- `.agents/config.json` — [Model ID, tool settings]
> Proceed? (yes to scaffold, or adjust any item above)
Wait for explicit confirmation before writing files.
Phase 3: Scaffold
Context Files (.gemini/GEMINI.md / .agents/AGENTS.md)
- This is the Master Context.
- Modularize via
@imports (e.g.,@[./docs/api-rules.md]) to keep your main agent file readable instead of one massive file.
What ships with it
5 files 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.
- 5d ago First seen · 104 lines · 99 tokens per session scan A 64c05627bb4f
antigravity-project-setup is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 909 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
close-issue
Close a GitHub or GitLab issue with a summary comment.
implement-issue
Implement a GitHub issue or GitLab issue and create a PR/MR.
gh-create-issue
Use when filing a GitHub issue for a bug, feature, audit, review finding, or investigated piece of work.
worktrees
Use when fanning several tickets into parallel branches and git worktrees, with related tickets grouped together.
architect
Staged build methodology for software projects: technical spike → design notes → build plan → stage-by-stage execution with professional-grade testing. Use when user says '/architect', 'new project', 'start a project', 'build this from scratch', wants to plan/build with structured methodology, or resumes an…