swarm

swarm is a skill for Claude Code, Codex from chhoumann/t3-pstack. It costs 41 tokens per session (1,007 once invoked), scanned A, original, MIT.

A coordinator for running several workers in parallel and combining their results into one report. Workers can explore separate parts of a task or try the same task independently.

In plain words
What is it for?
Use it for parallel code exploration, coverage checks, race-based reviews, and multi-part investigations.
Why use it?
It reduces the need to perform broad exploration or review one part at a time. The coordinator also defines the work and waits for all workers before reporting.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also reads $CODEX_HOME. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Part of the t3-pstack plugin — 62 skills, 4 agents, 1 hook shipped together

Good fit Use it for parallel code exploration, coverage checks, race-based reviews, and multi-part investigations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chhoumann/t3-pstack/swarm
Install

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.

Any agent
npx skills add chhoumann/t3-pstack --skill swarm
Clone the repo
git clone --depth 1 https://github.com/chhoumann/t3-pstack

Made for: Claude Code, Codex.

Or install t3-pstack, the plugin that ships this one along with the rest of its 62 skills, 4 agents, 1 hook.

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 swarm

README.md
[![agentmods](https://agentmods.dev/badge/skills/chhoumann/t3-pstack/swarm/github.svg)](https://agentmods.dev/skills/chhoumann/t3-pstack/swarm)
Your own site
<a href="https://agentmods.dev/skills/chhoumann/t3-pstack/swarm"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/swarm/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 swarm

Your own site · 80×15
<a href="https://agentmods.dev/skills/chhoumann/t3-pstack/swarm"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/swarm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,007 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.00041 $0.01007
Opus 5.5 $0.00016 $0.00403
Sonnet 5.5 $0.00008 $0.00201
Haiku 4.5 $0.00004 $0.00101

Measured yesterday against content hash 6f1e6d448eda, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

swarm 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 yesterday.

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.

plugins/pstack/skills/swarm/SKILL.md · 53 lines

How it starts

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

Swarm

Fan out N parallel workers. They may cover separate slices, race the same brief, or mix both. The parent waits, aggregates, and returns one report.

Start

Open a todolist with one entry per phase before launching anything.

  1. Frame
  2. Fan out
  3. Aggregate
  4. Report

Phase A: Frame

  1. State the done predicate and the artifact or report the swarm must return.
  2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare first pass, rank all, or best-of before spawning.
  3. Set N from the user or derive it from the shape. N is total workers, not the number that run at once.
  4. Pick the worker model from the swarm workers line in the model sheet. If the sheet or that line is missing, use the default in Models. For auto or inherit-parent, omit target so the workers run on the parent model. If delegate_task rejects an entry, use the default and say so. If it rejects the default, use another target of the same family from orchestrator_capabilities. For a model race, name each arm's model up front. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the poteto-mode skill.
  5. Give each worker its own writable output when it writes. When workers verify or measure commits, each brief names the exact SHAs. A measurement brief also names the method (sample count, what one sample is, order). The worker records both in its result.

Phase B: Fan out

Spawn all N workers in one response as delegate_task calls with mode: "async" and the step 4 target, left unset for auto or inherit-parent. Every worker runs on this machine, so a worker that writes gets its own git worktree, named by absolute path in its brief as the only place it writes.

When a worker must start from a non-default branch, create its worktree from that branch.

Every brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report. Reports use PASS, ISSUES, or BLOCKED with evidence. A worker that can prove a defect reports ISSUES and lists every issue it can prove, not only the first.

Read the full file on GitHub · 53 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. yesterday Changed · -7 lines 6f1e6d448eda
  2. 3d ago First seen · 60 lines · 41 tokens per session scan A 7d975bc77be8

Subscribe to this mod's changes

swarm is a skill published in the GitHub repository chhoumann/t3-pstack (190 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,007 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-10-13.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens