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/migratenpx skills add dsifry/metaswarm --skill migrategit 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/skills/dsifry/metaswarm/migrate)<a href="https://agentmods.dev/skills/dsifry/metaswarm/migrate"><img src="https://agentmods.dev/badge/skills/dsifry/metaswarm/migrate.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.00021 | $0.02577 |
| Opus 5 | $0.00010 | $0.01288 |
| Sonnet 5 | $0.00004 | $0.00515 |
| Haiku 4.5 | $0.00002 | $0.00258 |
Grade C, and why
migrate scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
git rm -rf .claude/plugins/metaswarm/ How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Skill
Migrate a project from npm-installed metaswarm (npx metaswarm init) to the marketplace plugin. Removes redundant embedded files with a safety protocol that prevents data loss.
When to use: The SessionStart hook detects .claude/plugins/metaswarm/.claude-plugin/plugin.json (legacy embedded plugin) and recommends running this skill.
IMPORTANT: Safety & Messaging Guidelines
The user MUST understand this before any file list is shown:
Before presenting any migration preview or file list, ALWAYS lead with this framing:
What this migration does: The marketplace plugin now provides all the skills, commands, rubrics, and guides that were previously copied into your project directory. This migration simply removes those redundant copies — the originals now live in the plugin itself.
Nothing is lost: Your project-specific files (CLAUDE.md, .coverage-thresholds.json, .beads/, bin/, scripts/) are NEVER touched. Only duplicate metaswarm framework files are removed.
Fully reversible: All removals are staged with
git rm(not permanently deleted). Before you commit:
- Undo everything:
git restore --staged . && git checkout -- .- After committing:
git revert HEADNo commit is made automatically — you review and commit when you're satisfied.
Tone: Be reassuring, not alarming. Say "cleaning up XX redundant copies" not "deleting XX files". Say "these files now live in the plugin" not "these files will be removed". Frame the migration as housekeeping, not destruction.
When showing file counts: If there are many files (e.g., 40+), explain that the large count is because the old npm installer copied the entire plugin framework into .claude/plugins/metaswarm/ — that one directory accounts for most of the count, and it's all framework code that's now served directly by the plugin.
Step 1: Pre-flight Check
- Confirm this skill is running from the marketplace plugin (if this skill loaded, the plugin is active)
- Read
.metaswarm/project-profile.json-- if"distribution": "plugin"is already set, inform the user migration was already completed and exit - Verify
.claude/plugins/metaswarm/.claude-plugin/plugin.jsonexists -- if not, there is nothing to migrate; inform the user and exit
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.
- 4d ago First seen · 260 lines · 21 tokens per session scan C 8b4e590a873e
migrate is a skill published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 2,577 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…