antigravity-superpowers: Skill for Claude Code

.agent/skills/dispatching-parallel-agents/SKILL.md

dispatching-parallel-agents is a skill for Claude Code, Codex from bonnguyenitc/antigravity-superpowers. It costs 26 tokens per session (1,445 once invoked), scanned A, a copy of dispatching-parallel-agents, MIT.

A method for assigning separate, independent software tasks to specialized agents so they can be investigated at the same time.

In plain words
What is it for?
Use it when investigating unrelated test failures, bugs, or project areas that can be handled independently.
Why use it?
It reduces unnecessary waiting when multiple problems do not depend on one another or share changing work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is bonnguyenitc/antigravity-superpowers's own configuration. It tells Claude Code and Codex how to work on antigravity-superpowers 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-superpowers configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bonnguyenitc/antigravity-superpowers. 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/bonnguyenitc/antigravity-superpowers/main/.agent/skills/dispatching-parallel-agents/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/bonnguyenitc/antigravity-superpowers

Made for: Claude Code, Codex.

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 dispatching-parallel-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/bonnguyenitc/antigravity-superpowers/dispatching-parallel-agents.svg)](https://agentmods.dev/skills/bonnguyenitc/antigravity-superpowers/dispatching-parallel-agents)
Your own site
<a href="https://agentmods.dev/skills/bonnguyenitc/antigravity-superpowers/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/antigravity-superpowers/dispatching-parallel-agents.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,445 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 91% copy Near-identical to another mod 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.00026 $0.01445
Opus 5 $0.00013 $0.00723
Sonnet 5 $0.00005 $0.00289
Haiku 4.5 $0.00003 $0.00145

Measured 8d ago against content hash 767e8f7442cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

dispatching-parallel-agents 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 8d 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

This is a copy

91% identical to dispatching-parallel-agents — 32 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.

.agent/skills/dispatching-parallel-agents/SKILL.md · 182 lines

How it starts

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

Dispatching Parallel Agents

Overview

You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.

When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.

Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.

When to Use

digraph when_to_use {
    "Multiple failures?" [shape=diamond];
    "Are they independent?" [shape=diamond];
    "Single agent investigates all" [shape=box];
    "One agent per problem domain" [shape=box];
    "Can they work in parallel?" [shape=diamond];
    "Sequential agents" [shape=box];
    "Parallel dispatch" [shape=box];

    "Multiple failures?" -> "Are they independent?" [label="yes"];
    "Are they independent?" -> "Single agent investigates all" [label="no - related"];
    "Are they independent?" -> "Can they work in parallel?" [label="yes"];
    "Can they work in parallel?" -> "Parallel dispatch" [label="yes"];
    "Can they work in parallel?" -> "Sequential agents" [label="no - shared state"];
}

Use when:

  • 3+ test files failing with different root causes
  • Multiple subsystems broken independently
  • Each problem can be understood without context from others
  • No shared state between investigations

Don't use when:

  • Failures are related (fix one might fix others)
  • Need to understand full system state
  • Agents would interfere with each other

The Pattern

1. Identify Independent Domains

Group failures by what's broken:

  • File A tests: Tool approval flow
  • File B tests: Batch completion behavior
  • File C tests: Abort functionality

Each domain is independent - fixing tool approval doesn't affect abort tests.

Read the full file on GitHub · 182 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. 8d ago First seen · 182 lines · 26 tokens per session scan A 767e8f7442cc

Subscribe to this mod's changes

dispatching-parallel-agents is a skill published in the GitHub repository bonnguyenitc/antigravity-superpowers (19 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,445 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to dispatching-parallel-agents, differing in 32 lines, and is treated as a copy.

Related

Other skills, from other repositories

codeck

Route explicit requests from a host coding agent to one or more locally configured AI executors through Codeck, attach Markdown or other project files, moderate cross-model consultation, expose disagreements, and synthesize traceable results. Use when the user explicitly names Codeck or asks to consult, compare, or…

isdou/codeck · 108 tokens

openai-docs

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…

rojim666/SztuCode · 105 tokens

control-chrome

Control the user's Chrome browser for tasks that depend on existing Chrome state: tabs, logged-in sessions, or extensions. Prefer purpose-built connectors, APIs, or CLIs when available.

rojim666/SztuCode · 40 tokens

Presentations

Read, create or edit PowerPoint or Google Slides decks. Use for presentation, slide deck, PowerPoint, PPT, PPTX, or Google Slides requests.

rojim666/SztuCode · 35 tokens

Spreadsheets

Create, edit, analyze, and verify standalone spreadsheet files or Google Sheets-ready workbooks, including .xlsx, .xls, .csv, and .tsv. Do not use for live controlling Microsoft Excel app or a live Excel session.

rojim666/SztuCode · 52 tokens

template-creator

Create or update a reusable personal Codex artifact-template skill. Use when the user invokes $template-creator or asks in natural language to create a reusable template from a reference document, presentation, spreadsheet, ImageGen or Product Design image, email, or Slack message, or explicitly asks to edit or update…

rojim666/SztuCode · 82 tokens