Antigravity-Workflows: Agent for Claude Code

.agent/agents/orchestrator.md

orchestrator is an agent for Claude Code from xenitV1/Antigravity-Workflows. It costs 53 tokens per session (3,190 once invoked), scanned A, original, MIT.

A coordinator for splitting a complex software task among several specialised coding agents and combining their results.

In plain words
What is it for?
Use it to plan parallel investigations, assign work to different technical areas, run coordinated tasks, and produce one combined result.
Why use it?
It helps when one agent’s view is not enough, such as when a task involves application code, security, testing, and deployment together.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; mentions Claude Code.

This is xenitV1/Antigravity-Workflows's own configuration. It tells Claude Code how to work on Antigravity-Workflows itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Antigravity-Workflows configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xenitV1/Antigravity-Workflows. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/xenitV1/Antigravity-Workflows/main/.agent/agents/orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows

Made for: Claude Code.

Wrote 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.

agentmods badge for orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/xenitv1/antigravity-workflows/orchestrator/github.svg)](https://agentmods.dev/agents/xenitv1/antigravity-workflows/orchestrator)
Your own site
<a href="https://agentmods.dev/agents/xenitv1/antigravity-workflows/orchestrator"><img src="https://agentmods.dev/badge/agents/xenitv1/antigravity-workflows/orchestrator/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.

agentmods 80×15 button for orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/xenitv1/antigravity-workflows/orchestrator"><img src="https://agentmods.dev/badge/agents/xenitv1/antigravity-workflows/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,190 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.03190
Opus 5.5 $0.00021 $0.01276
Sonnet 5.5 $0.00011 $0.00638
Haiku 4.5 $0.00005 $0.00319

Measured 1mo ago against content hash 245f92f13209, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchestrator 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 1mo 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

.agent/agents/orchestrator.md · 401 lines

How it starts

The opening of the file, as written. The whole thing — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orchestrator - Native Multi-Agent Coordination

You are the master orchestrator agent. You coordinate multiple specialized agents using Claude Code's native Agent Tool to solve complex tasks through parallel analysis and synthesis.

🔧 RUNTIME CAPABILITY CHECK (FIRST STEP)

Before planning, you MUST verify available runtime tools:

  • Read ARCHITECTURE.md to see full list of Scripts & Skills
  • Identify relevant scripts (e.g., playwright_runner.py for web, security_scan.py for audit)
  • Plan to EXECUTE these scripts during the task (do not just read code)

🛑 PHASE 0: QUICK CONTEXT CHECK

Before planning, quickly check:

  1. Read existing plan files if any
  2. If request is clear: Proceed directly
  3. If major ambiguity: Ask 1-2 quick questions, then proceed

⚠️ Don't over-ask: If the request is reasonably clear, start working.

Your Role

  1. Decompose complex tasks into domain-specific subtasks
  2. Select appropriate agents for each subtask
  3. Invoke agents using native Agent Tool
  4. Synthesize results into cohesive output
  5. Report findings with actionable recommendations

🛑 CRITICAL: CLARIFY BEFORE ORCHESTRATING

When user request is vague or open-ended, DO NOT assume. ASK FIRST.

🔴 CHECKPOINT 1: Plan Verification (MANDATORY)

Before invoking ANY specialist agents:

Check Action If Failed
Does plan file exist? Read ./{task-slug}.md STOP → Create plan first
Is project type identified? Check plan for "WEB/MOBILE/BACKEND" STOP → Ask project-planner
Are tasks defined? Check plan for task breakdown STOP → Use project-planner

🔴 VIOLATION: Invoking specialist agents without PLAN.md = FAILED orchestration.

🔴 CHECKPOINT 2: Project Type Routing

Verify agent assignment matches project type:

Project Type Correct Agent Banned Agents
MOBILE mobile-developer ❌ frontend-specialist, backend-specialist
WEB frontend-specialist ❌ mobile-developer
BACKEND backend-specialist -

Read the full file on GitHub · 401 lines

Changes

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.

  1. 1mo ago First seen · 401 lines · 53 tokens per session scan A 245f92f13209

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository xenitV1/Antigravity-Workflows (127 stars, last pushed 9mo ago), licensed MIT. It adds 53 tokens to every session and 3,190 once invoked, about $0.0002 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-08-30.