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 commands/dsifry/metaswarm/metaswarm-setupgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/commands/dsifry/metaswarm/metaswarm-setup)<a href="https://agentmods.dev/commands/dsifry/metaswarm/metaswarm-setup"><img src="https://agentmods.dev/badge/commands/dsifry/metaswarm/metaswarm-setup.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.05523 |
| Opus 5 | $0.00000 | $0.02762 |
| Sonnet 5 | $0.00000 | $0.01105 |
| Haiku 4.5 | $0.00000 | $0.00552 |
Grade A, and why
metaswarm-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 5d 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 — 601 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metaswarm Guided Setup
Interactive, Claude-guided setup for metaswarm in your project. Detects your stack, asks targeted questions, and customizes everything automatically.
Usage
/metaswarm-setup
Phase 1: Bootstrap Check
Before anything else, verify that metaswarm components are installed.
Step 1.1 — Check for plugin directory
Use the Glob tool to check if .claude/plugins/metaswarm/ exists:
Glob: .claude/plugins/metaswarm/**/*
- If files are found, metaswarm components are installed. Proceed to Step 1.2.
- If NO files are found, tell the user: "Metaswarm components aren't installed yet. Let me install them now." Then run via Bash:
npx metaswarm install
Wait for the command to complete. If it fails, tell the user to check their Node.js installation and try npm install -g metaswarm manually.
Step 1.2 — Check for existing project profile
Use the Glob tool to check if .metaswarm/project-profile.json exists.
- If it exists, read it and present the current configuration summary to the user. Use AskUserQuestion to ask:
- "You already have a metaswarm project profile. What would you like to do?"
- Options: "Re-run setup (Recommended)" / "Skip setup"
- If user chooses "Skip setup", stop here with: "Setup skipped. Your existing configuration is unchanged."
- If user chooses "Re-run setup", continue to Phase 2.
- If it does NOT exist, continue to Phase 2.
Phase 2: Project Detection
You MUST detect all of the following automatically by scanning the project directory. Use the Glob and Read tools — do NOT ask the user for any of this information. Detect everything silently, then present the results.
2.1 — Language Detection
Check for these marker files using Glob at the project root:
| Marker File | Language |
|---|---|
package.json |
Node.js / JavaScript |
tsconfig.json |
TypeScript (refines Node.js to TypeScript) |
pyproject.toml OR setup.py OR requirements.txt |
Python |
go.mod |
Go |
Cargo.toml |
Rust |
pom.xml OR build.gradle OR build.gradle.kts |
Java |
Gemfile |
Ruby |
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.
- 5d ago First seen · 601 lines · 0 tokens per session scan A 965ecf70abda
metaswarm-setup is a command published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,523 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.