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 Ghosteken/agent-harness --skill antigravity-agent-managergit clone --depth 1 https://github.com/Ghosteken/agent-harnessWrote 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/ghosteken/agent-harness/antigravity-agent-manager)<a href="https://agentmods.dev/skills/ghosteken/agent-harness/antigravity-agent-manager"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/antigravity-agent-manager/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/ghosteken/agent-harness/antigravity-agent-manager"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/antigravity-agent-manager.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.00030 | $0.01241 |
| Opus 5 | $0.00015 | $0.00620 |
| Sonnet 5 | $0.00006 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
antigravity-agent-manager 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.
This is a copy
92% identical to antigravity-agent-manager — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity Agent Manager
Overview
A playbook for orchestrating multi-agent systems using the standalone Antigravity 2.0 Agent Manager (white icon) in parallel with the Antigravity IDE (black icon).
Starting with version 2.0, Google decoupled the Agent Manager from the main IDE interface, removing the "Open Agent Manager" button. This skill outlines how to install, configure, and operate the two environments side-by-side to direct multiple AI agents on front-end and back-end projects simultaneously.
When to Use This Skill
- Use when you need to coordinate multiple front-end, back-end, or QA agents working on the same codebase simultaneously.
- Use when setting up the dual-window workspace (Antigravity IDE + Antigravity 2.0 Agent Manager).
- Use to resolve conflicts or obsolete tutorial steps that mention the integrated "Open Agent Manager" button.
How It Works
Step 1: Parallel Installation
- Keep your current Antigravity IDE: Do not uninstall the classic IDE (black icon).
- Download Antigravity 2.0: Fetch the standalone Agent Manager application from the official Antigravity downloads page.
- Install: Run the installer. It will install alongside your existing IDE without overwriting it. You should now have both:
- Antigravity IDE (Black Icon) — Your code editor and manual development workspace.
- Antigravity 2.0 (White Icon) — Your multi-agent orchestrator dashboard.
Step 2: Dual-Workspace Setup
- Open both the Antigravity IDE and Antigravity 2.0 applications.
- Load the same project directory (e.g.,
C:/Users/erwinpzocikk/Dev/GroupProjects/intIntercatedraAdmin) in both apps. - In the Agent Manager (white icon), configure your Agent pool. Assign specialized roles (e.g.,
frontend-agent,backend-agent,qa-validator).
Step 3: Coordinating Agent Execution
- In the Agent Manager, define the task scopes. To prevent directory conflicts and race conditions:
- Assign the
backend-agentto the server directory (e.g.,/serveror/api). - Assign the
frontend-agentto the frontend directory (e.g.,/clientor/src).
- Assign the
- Run the agents in parallel.
- Use the Antigravity IDE (black icon) to monitor file changes in real-time, review diffs, and perform manual tweaks.
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 · 112 lines · 30 tokens per session scan A ed485ee80abc
antigravity-agent-manager is a skill published in the GitHub repository Ghosteken/agent-harness (2 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 1,241 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to antigravity-agent-manager, differing in 19 lines, and is treated as a copy.
Other skills, from other repositories
antigravity-agent-manager
Configure and orchestrate parallel agents using the standalone Antigravity 2.0 Agent Manager and Antigravity IDE.
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
agent-team-handoff
A workflow for coordinating several AI assistants or agents on one project. It uses shared handoff files to record the current task, roles, decisions, progress, next steps, and proof of completion.
hyperflow
Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, or another single-agent surface. Auto-invoke for non-trivial engineering work: build, implement, add, refactor, debug, fix, review, audit, plan, scope, design, brainstorm, ship, or deploy. Trigger with /hyperflow:hyperflow, "use…
atmos-migration
This skill helps you migrate a repository to Atmos. It covers native Terraform, Terraform Workspaces, Terramate, Terragrunt, Makefiles, Justfiles, and Taskfiles. It gives minimum-disruption paths, file-layout options, workspace mapping, task-to-command mapping, generatehcl/script decomposition, and the remote-state…
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.