A diagnostic report for checking metaswarm's installation and project configuration across Claude Code, Codex, and Gemini. It reports the detected version, setup state, and possible problems.

Use it to verify whether metaswarm is installed and configured correctly. It checks the active platform, plugin files, project profile, and other relevant setup details.

It gathers setup information in one place instead of requiring separate manual checks. This makes installation, migration, and configuration issues easier to investigate.

status — Skill for Claude Code and Codex by dsifry: A diagnostic report for checking metaswarm's installation and project…

Install

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.

agentmods

npx agentmods add skills/dsifry/metaswarm/status

Any agent

npx skills add dsifry/metaswarm --skill status

Clone the repo

git clone --depth 1 https://github.com/dsifry/metaswarm

Made for: Claude Code, Codex.

Or install metaswarm, the plugin that ships this one along with the rest of its 14 skills, 16 commands, 19 agents, 2 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dsifry/metaswarm/status.svg)](https://agentmods.dev/skills/dsifry/metaswarm/status)

Your own site

<a href="https://agentmods.dev/skills/dsifry/metaswarm/status"><img src="https://agentmods.dev/badge/skills/dsifry/metaswarm/status.svg" alt="Measured on agentmods" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,569 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00018	$0.01569
Opus 5	$0.00009	$0.00785
Sonnet 5	$0.00004	$0.00314
Haiku 4.5	$0.00002	$0.00157

Measured 4d ago against content hash 79ee564774d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

status scanned grade B 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- Check `~/.codex/config.toml` for an enabled `metaswarm@...` plugin entry when accessible

skills/status/SKILL.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Status Skill

Generate a diagnostic report of the metaswarm installation, project configuration, and potential issues across Claude Code, Codex, and Gemini. Useful for troubleshooting and verifying setup or migration.

Checks

Run each check below and present results in a single formatted report. Detect the active platform first:

Codex: PLUGIN_ROOT or CODEX_HOME is present, .codex-plugin/plugin.json is the active manifest, or the user invoked $status
Claude Code: CLAUDE_PLUGIN_ROOT is present, .claude-plugin/plugin.json is the active manifest, or the user invoked $status
Gemini: extensionPath is present, gemini-extension.json is the active manifest, or the user invoked $status

1. Plugin Version

Codex: read .codex-plugin/plugin.json from the plugin root and report version
Claude Code: read .claude-plugin/plugin.json from the plugin root and report version
Gemini: read gemini-extension.json from the plugin root and report version
Fallback: read package.json at plugin root for version
If neither found: Plugin version: UNKNOWN

2. Project Setup State

Check if .metaswarm/project-profile.json exists in the working directory
If present, report key fields: distribution, metaswarm_version, language, framework, test_runner
If absent, report the platform-specific setup command:
- Codex: Project setup: NOT CONFIGURED -- run $setup
- Claude Code: Project setup: NOT CONFIGURED -- run $setup
- Gemini: Project setup: NOT CONFIGURED -- run $setup

3. Platform Install State

Codex

Check .codex-plugin/plugin.json exists in the plugin root
Check ~/.codex/config.toml for an enabled metaswarm@... plugin entry when accessible
Scan ~/.codex/plugins/cache/ for .codex-plugin/plugin.json with "name": "metaswarm"
If installed from a local marketplace, report cache version as local

Claude Code

Check .claude-plugin/plugin.json exists in the plugin root
Scan ~/.claude/plugins/cache/ for .claude-plugin/plugin.json with "name": "metaswarm"
Report marketplace/plugin cache status when accessible

Read the full file on GitHub · 174 lines

Changes

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 · 174 lines · 18 tokens per session scan B 79ee564774d9

Subscribe to this mod's changes

status is a skill published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,569 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

status