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.
git 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-update-version)<a href="https://agentmods.dev/commands/dsifry/metaswarm/metaswarm-update-version"><img src="https://agentmods.dev/badge/commands/dsifry/metaswarm/metaswarm-update-version.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.1 | $0.00000 | $0.00643 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
metaswarm-update-version 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Metaswarm
Update metaswarm to the latest version, refresh component files, and re-detect project context.
Usage
/metaswarm-update-version
Steps
1. Check Current Version
- Read
.metaswarm/project-profile.jsonand extractmetaswarm_version - If the file doesn't exist, stop and tell the user:
No project profile found. Run
/metaswarm-setupfirst to initialize metaswarm. - Display the current version to the user
2. Fetch Latest Version
- Run
npm view metaswarm versionto get the latest published version - Compare current vs. latest:
- If current == latest: tell the user they're already up to date and stop
- If current < latest: continue to the next step
3. Show What's New
- Run
npx metaswarm@latest changelog --from <current-version>to show changes between versions - If that fails, try
npx metaswarm@latest changelogand filter entries after the current version - Highlight any BREAKING CHANGES prominently if present
- Show a summary of new features, fixes, and new components
4. Update Files
- Run
npx metaswarm@latest installto refresh all component files - This uses skip-if-exists semantics — user customizations in CLAUDE.md, agents, etc. are preserved
- New files (new skills, commands, agents, guides) will be added
- Existing metaswarm-shipped files will be refreshed to latest versions
5. Re-detect Project Context
- Re-run project detection from the setup flow:
- Language, framework, test runner, linter, formatter, package manager, type checker, CI, git hooks
- Compare new detection results against
detectionin the existing project profile - If changes are detected (e.g., project switched from Jest to Vitest):
- Show what changed
- Ask user if they want to re-customize affected files (e.g., update coverage commands in CLAUDE.md)
- If yes, apply the same customization logic from
/metaswarm-setup
6. Update Project Profile
- Update
.metaswarm/project-profile.json:metaswarm_version→ set to new versionupdated_at→ set to current ISO 8601 timestampdetection→ refresh if project context changed (preserve if unchanged)
- Preserve all other fields (
installed_at,choices,commands, etc.)
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.
- 8d ago First seen · 68 lines · 0 tokens per session scan A 144406a11f78
metaswarm-update-version is a command published in the GitHub repository dsifry/metaswarm (413 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 643 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.