Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/friedbotstudio/baseline/main/.claude/skills/swarm-dispatch/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/swarm-dispatch)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/swarm-dispatch"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/swarm-dispatch/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/friedbotstudio/baseline/swarm-dispatch"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/swarm-dispatch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.03640 |
| Opus 5.5 | $0.00034 | $0.01456 |
| Sonnet 5.5 | $0.00017 | $0.00728 |
| Haiku 4.5 | $0.00008 | $0.00364 |
Grade A, and why
swarm-dispatch 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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-dispatch — wave runner with worktree isolation
Invoked after /swarm-plan + /approve-swarm. The architecture is the user's principle made concrete:
Main context decides. Workers execute.
Per task, before dispatch, you (main context) produce two recipes:
- The scenario recipe — exactly which failing tests the worker should write.
- The implementation contract — exactly which source files the worker may touch and what behavior they must implement.
The worker's prompt contains both recipes verbatim. The worker invokes Skill(scenario) then Skill(implement) and reports JSON. It makes no design decisions.
Isolation modes
Read project.json → swarm.isolation (default "auto"):
"auto"→ chooseworktreeif the project root is inside a git repo (git rev-parse --is-inside-work-treesucceeds), elseshared."worktree"→ require a git repo; bail if absent."shared"→ never use worktrees; rely onswarm_boundary_guardfor runtime enforcement.
Default path is worktree. The rest of this document describes that mode. The shared fallback is at the end.
Worktree mode = single-wave only (D1). The worktree base commit is chosen by the Agent tool's
isolation:"worktree", not by baseline (observed forking from a stale ref on the first real swarm run), andswarm_merge.mjsapplies wave output without committing — so a multi-wave worktree plan's wave-N+1 worktrees branch from a base lacking wave-N output. Baseline cannot fix this, only refuse it. Before dispatch, callassertWorktreeWaveSafety({isolation, waves, baselineRef, worktreeBase})from.claude/skills/swarm-dispatch/worktree-safety.mjs(worktreeBase =git -C <wt> merge-base HEAD <wt-HEAD>once a worktree exists). Onok:false(multi-wave under worktree, orbaseline_ref≠ the worktree's real merge-base), abort and steer the plan to shared isolation — do not run the wave. Multi-wave plans belong insharedmode.
Prereqs (worktree mode)
What ships with it
4 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.
- 1mo ago First seen · 236 lines · 84 tokens per session scan A a3e38191fd4c
swarm-dispatch is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 84 tokens to every session and 3,640 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
finishing-a-development-branch
Open a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.
ca-audit
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
ca-chore
Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.
gh-issues
Use when turning a diagnose.buildpacket.v1 JSON packet, bug diagnosis, or agent handoff into GitHub issues or issue comments, especially when the user wants ready-for-agent work items created without implementing code.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
triage-issues
Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content.