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 agentmods add skills/dsifry/metaswarm/setupnpx skills add dsifry/metaswarm --skill setupgit clone --depth 1 https://github.com/dsifry/metaswarmWhat 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 | $0.00019 | $0.05080 |
| Opus 5 | $0.00010 | $0.02540 |
| Sonnet 5 | $0.00004 | $0.01016 |
| Haiku 4.5 | $0.00002 | $0.00508 |
Grade A, and why
setup 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 2d 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 — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Interactive setup for metaswarm. Detects your stack, asks targeted questions, writes project-local files, and creates platform-appropriate instruction files and command shims. Replaces both npx metaswarm init and the old /metaswarm-setup command.
After Phase 2 (user questions), determine the correct coverage command from the detection results, then run this Bash command:
PLUGIN_ROOT="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-${extensionPath:-}}}"
if [ -z "$PLUGIN_ROOT" ]; then
setup_script="$(find "${CODEX_HOME:-$HOME/.codex}/plugins/cache" -path '*/metaswarm/*/lib/setup-mandatory-files.sh' -print -quit 2>/dev/null)"
if [ -n "$setup_script" ]; then
PLUGIN_ROOT="$(cd "$(dirname "$setup_script")/.." && pwd)"
fi
fi
if [ -z "$PLUGIN_ROOT" ] && [ -f "$(pwd)/lib/setup-mandatory-files.sh" ]; then
PLUGIN_ROOT="$(pwd)"
fi
bash "${PLUGIN_ROOT}/lib/setup-mandatory-files.sh" "$(pwd)" <threshold> "<coverage-command>" --platform <platform>
Where:
<threshold>is the user's chosen percentage (e.g.,100)<coverage-command>is the enforcement command for their test runner:- pytest →
"pytest --cov --cov-fail-under=<threshold>" - vitest/pnpm →
"pnpm vitest run --coverage" - jest/npm →
"npx jest --coverage" - go →
"go test -coverprofile=coverage.out ./..." - cargo →
"cargo tarpaulin --fail-under <threshold>"
- pytest →
<platform>iscodex,claude,gemini, orall. Prefer:codexwhen running in Codex (PLUGIN_ROOTorCODEX_HOMEis present, or the user invoked$setup)claudewhen running in Claude Code (CLAUDE_PLUGIN_ROOTis present, or the setup skill was invoked there)geminiwhen running in Gemini (extensionPathis present, or the setup skill was invoked there)allonly when the user explicitly asks to configure every supported CLI
The script handles:
- Instruction file —
AGENTS.mdfor Codex,CLAUDE.mdfor Claude,GEMINI.mdfor Gemini; appends metaswarm section (or writes new), skips if already present .coverage-thresholds.json— writes at project root with correct thresholds and command- Claude command shims — for Claude/all only, writes
.claude/commands/start-task.md,prime.md,review-design.md,self-reflect.md,pr-shepherd.md,brainstorm.md
The script outputs JSON with what was created/skipped/errored. Check that "status": "ok".
If the script is not available or fails, fall back to writing these files manually with the Write tool. Do NOT skip them.
What ships with it
35 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.
- bin/estimate-cost.sh 1.8 KB runs code
- bin/external-tools-verify.sh 5.5 KB runs code
- bin/pr-comments-check.sh 2.7 KB runs code
- bin/pr-comments-filter.sh 6.6 KB runs code
- knowledge/anti-patterns.jsonl 840 B
- knowledge/api-behaviors.jsonl 834 B
- knowledge/codebase-facts.jsonl 899 B
- knowledge/decisions.jsonl 919 B
- knowledge/facts.jsonl 866 B
- knowledge/gotchas.jsonl 888 B
- knowledge/patterns.jsonl 893 B
- knowledge/README.md 3.8 KB
- scripts/beads-fetch-conversation-history.ts 13 KB runs code
- scripts/beads-fetch-pr-comments.ts 9.5 KB runs code
- templates/.env.example 249 B
- templates/AGENTS-append.md 2.2 KB
- templates/AGENTS.md 4.8 KB
- templates/beads-developer-setup.md 7.9 KB
- templates/beads-readme.md 2.7 KB
- templates/ci-coverage-job.yml 4.1 KB
- templates/ci.yml 1.6 KB
- templates/CLAUDE-append.md 3.8 KB
- templates/CLAUDE.md 12 KB
- templates/coverage-thresholds.json 607 B
- templates/external-tools-setup.md 9.8 KB
- templates/external-tools.yaml 1.3 KB
- templates/GEMINI-append.md 2.4 KB
- templates/GEMINI.md 5.1 KB
- templates/gitignore 294 B
- templates/gtg-workflow.yml 2.3 KB
- templates/pre-push 1.9 KB
- templates/SERVICE-INVENTORY.md 1.3 KB
- templates/task-completion-checklist.md 6.9 KB
- templates/todo-management.md 3.7 KB
- templates/UI-FLOWS.md 1.9 KB
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.
- 2d ago First seen · 469 lines · 19 tokens per session scan A 26a2660be6c1
setup is a skill published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 5,080 once invoked, about $0.0001 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.