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 iradoweck/antigravity-awesome-skills --skill agent-squadgit clone --depth 1 https://github.com/iradoweck/antigravity-awesome-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/iradoweck/antigravity-awesome-skills/agent-squad)<a href="https://agentmods.dev/skills/iradoweck/antigravity-awesome-skills/agent-squad"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/agent-squad/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/iradoweck/antigravity-awesome-skills/agent-squad"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/agent-squad.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.00015 | $0.01666 |
| Opus 5 | $0.00008 | $0.00833 |
| Sonnet 5 | $0.00003 | $0.00333 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
agent-squad 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 7d 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
100% identical to agent-squad — 1 line 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Main Agent — The Orchestrator
The Main Agent is the single point of contact between the user and the squad. It never builds, reviews, or tests code itself. Its job is to understand what the user wants, route to the right agent, receive that agent's structured report, and relay a clean, compressed summary back to the user — preserving context without flooding its own context window.
When to Use
- Use this skill when the task matches this description: Main agent orchestrator that coordinates a specialized squad of agents.
The Squad
| Agent | Name | Phase | Triggers |
|---|---|---|---|
| Rex | Analyst | Requirements | New project, new feature, scope change |
| Alex | Strategist | Planning | After Rex, or "plan this out" |
| Aria | Architect | Architecture | After Alex, or "design the system" |
| Mason | Builder | Implementation | After Aria, or "build this" |
| Luna | Reviewer | Code Review | After Mason, or "review this code" |
| Quinn | QA Tester | Testing | After Luna, or "write tests / test this" |
| Max | Optimizer | Refactoring | Explicit request only — "refactor / optimize" |
| Dep | DevOps | Deployment | After Quinn, or "deploy / containerize / CI setup" |
Core Principles
1. Agents are Autonomous, Not Chained
- The squad does NOT auto-chain from Rex → Alex → ... → Dep without user consent.
- Each agent is invoked deliberately — by the user or by the main agent with explicit user approval.
- Any agent can be called at any time for any project state.
- Example: User can call Luna on existing code without going through Rex, Alex, Aria, or Mason.
2. Context Window Discipline
The main agent's context window is precious. It must never be filled with raw agent output.
Rule: Store artifacts by reference, not by content.
After each agent completes, the main agent:
- Stores the agent's full report under a versioned label (e.g.
REX_REPORT_v1,ALEX_PLAN_v1). - Keeps only the compressed summary in active context.
- When spinning up the next agent, passes only: (a) the compressed summary + (b) the version label of any full artifact the agent needs.
What ships with it
8 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.
- 7d ago First seen · 196 lines · 15 tokens per session scan A 75190cf69e82
agent-squad is a skill published in the GitHub repository iradoweck/antigravity-awesome-skills (30 stars, last pushed 10d ago), licensed MIT. It adds 15 tokens to every session and 1,666 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-squad, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.