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 git-pr-workflows-git-workflowgit 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/git-pr-workflows-git-workflow)<a href="https://agentmods.dev/skills/rmyndharis/antigravity-skills/git-pr-workflows-git-workflow"><img src="https://agentmods.dev/badge/skills/rmyndharis/antigravity-skills/git-pr-workflows-git-workflow/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/git-pr-workflows-git-workflow"><img src="https://agentmods.dev/badge/skills/rmyndharis/antigravity-skills/git-pr-workflows-git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 33 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00037 | $0.02154 |
| Opus 5.5 | $0.00015 | $0.00862 |
| Sonnet 5.5 | $0.00007 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
git-pr-workflows-git-workflow 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- git-pr-workflows-git-workflow — 100% identical, 2 lines differ
- git-pr-workflows-git-workflow — 97% identical, 6 lines differ
- git-pr-workflows-git-workflow — 97% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Git Workflow with Multi-Agent Orchestration
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.
[Extended thinking: This workflow coordinates multiple specialized agents to ensure code quality before commits are made. The code-reviewer agent performs initial quality checks, test-automator ensures all tests pass, and deployment-engineer verifies production readiness. By orchestrating these agents sequentially with context passing, we prevent broken code from entering the repository while maintaining high velocity. The workflow supports both trunk-based and feature-branch strategies with configurable options for different team needs.]
Use this skill when
- Working on complete git workflow with multi-agent orchestration tasks or workflows
- Needing guidance, best practices, or checklists for complete git workflow with multi-agent orchestration
Do not use this skill when
- The task is unrelated to complete git workflow with multi-agent orchestration
- 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.
Configuration
Target branch: $ARGUMENTS (defaults to 'main' if not specified)
Supported flags:
--skip-tests: Skip automated test execution (use with caution)--draft-pr: Create PR as draft for work-in-progress--no-push: Perform all checks but don't push to remote--squash: Squash commits before pushing--conventional: Enforce Conventional Commits format strictly--trunk-based: Use trunk-based development workflow--feature-branch: Use feature branch workflow (default)
Phase 1: Pre-Commit Review and Analysis
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 Changed · -4 tokens per session 6b39114da588
- 1mo ago First seen · 140 lines · 41 tokens per session scan A 263a10d1a418
git-pr-workflows-git-workflow is a skill published in the GitHub repository rmyndharis/antigravity-skills (1,809 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 2,154 once invoked, about $0.0001 per session on Opus 5.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
github
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
pr-review
Review pull requests and Git diffs with Graph-It-Live risk, breaking-change, dependency-impact, cycle, unused-export, and test-candidate evidence. Use when asked to review a PR, inspect a diff, assess merge risk, check a branch before merging, create a Graph-It-Live review gate, or explain review-pr results. Trigger…
conventional-commits
Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.
mindforge-ship
Create PR, run review, and prepare for merge after verification passes.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
app-store-changelog
Generate user-facing App Store release notes from git history since the last tag.