Antigravity Skill Vault is a collection of reusable Agent Skills for Google Antigravity, covering software development, operations, security, and business work. It is for people who want Antigravity agents to follow specialized expertise, personas, and structured workflows. The catalogue skills are entries from this collection.
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 rmyndharis/antigravity-skills --skill conductor-implementgit clone --depth 1 https://github.com/rmyndharis/antigravity-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/rmyndharis/antigravity-skills/conductor-implement)<a href="https://agentmods.dev/skills/rmyndharis/antigravity-skills/conductor-implement"><img src="https://agentmods.dev/badge/skills/rmyndharis/antigravity-skills/conductor-implement/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/rmyndharis/antigravity-skills/conductor-implement"><img src="https://agentmods.dev/badge/skills/rmyndharis/antigravity-skills/conductor-implement.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 Excessive Agency · line 382 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00017 | $0.02194 |
| Opus 5 | $0.00009 | $0.01097 |
| Sonnet 5 | $0.00003 | $0.00439 |
| Haiku 4.5 | $0.00002 | $0.00219 |
Grade A, and why
conductor-implement 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- conductor-implement — 95% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Track
Execute tasks from a track's implementation plan, following the workflow rules defined in conductor/workflow.md.
Use this skill when
- Working on implement track tasks or workflows
- Needing guidance, best practices, or checklists for implement track
Do not use this skill when
- The task is unrelated to implement track
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
Pre-flight Checks
-
Verify Conductor is initialized:
- Check
conductor/product.mdexists - Check
conductor/workflow.mdexists - Check
conductor/tracks.mdexists - If missing: Display error and suggest running
/conductor:setupfirst
- Check
-
Load workflow configuration:
- Read
conductor/workflow.md - Parse TDD strictness level
- Parse commit strategy
- Parse verification checkpoint rules
- Read
Track Selection
If argument provided:
- Validate track exists:
conductor/tracks/{argument}/plan.md - If not found: Search for partial matches, suggest corrections
If no argument:
-
Read
conductor/tracks.md -
Parse for incomplete tracks (status
[ ]or[~]) -
Display selection menu:
Select a track to implement: In Progress: 1. [~] auth_20250115 - User Authentication (Phase 2, Task 3) Pending: 2. [ ] nav-fix_20250114 - Navigation Bug Fix 3. [ ] dashboard_20250113 - Dashboard Feature Enter number or track ID:
Context Loading
Load all relevant context for implementation:
-
Track documents:
conductor/tracks/{trackId}/spec.md- Requirementsconductor/tracks/{trackId}/plan.md- Task listconductor/tracks/{trackId}/metadata.json- Progress state
-
Project context:
conductor/product.md- Product understandingconductor/tech-stack.md- Technical constraintsconductor/workflow.md- Process rules
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.
- 9d ago First seen · 388 lines · 17 tokens per session scan A 73542497e96b
conductor-implement is a skill published in the GitHub repository rmyndharis/antigravity-skills (1,502 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 2,194 once invoked, about $0.0001 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
test-driven-execution
Before writing any implementation code, define the acceptance criteria and test cases that the code must satisfy. Agents then write code to pass these tests — not to match a vague description. Eliminates "it works on my machine" and "I think this is what you wanted" outcomes.
tdd
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/ /, verify APIs via web search, then implement in tiny test-verified steps.
tdd-practitioner
Practice Test-Driven Development with the red-green-refactor cycle. Write tests before code to drive better design, coverage, and confidence.
tdd-full-cycle
Group skill: Test-Driven Development full cycle — plan, RED phase, GREEN phase, REFACTOR phase, E2E tests, coverage, and review.
acceptance-orchestrator
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.