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 skills add dsifry/metaswarm --skill startgit 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/start)<a href="https://agentmods.dev/skills/dsifry/metaswarm/start"><img src="https://agentmods.dev/badge/skills/dsifry/metaswarm/start/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dsifry/metaswarm/start"><img src="https://agentmods.dev/badge/skills/dsifry/metaswarm/start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 249 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 660 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00027 | $0.07169 |
| Opus 5.5 | $0.00011 | $0.02868 |
| Sonnet 5.5 | $0.00005 | $0.01434 |
| Haiku 4.5 | $0.00003 | $0.00717 |
Grade A, and why
start 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 1mo 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 — 872 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BEADS Multi-Agent Orchestration Skill
This skill coordinates a swarm of specialized AI agents to autonomously handle GitHub Issues from creation to merged PR.
Quick Start
Start Work on a GitHub Issue
# User triggers via any of:
@beads start #123
bd start 123
/beads-start 123
Check BEADS Status
bd ready # Show tasks ready to work
bd list # Show all tasks
bd stats # Show project statistics
bd doctor # Check system health
Agent Roster
| Agent | Role | Spawned When |
|---|---|---|
| Issue Orchestrator | Main coordinator per Issue | Issue receives agent-ready label |
| Researcher Agent | Codebase exploration | Orchestrator creates research task |
| Architect Agent | Implementation planning | Research complete |
| Product Manager Agent | Use case & user benefit review | Design review gate (parallel) |
| Designer Agent | UX/API design review | Design review gate (parallel) |
| Security Design Agent | Security threat modeling | Design review gate (parallel) |
| CTO Agent | TDD readiness & plan review | Design review gate (parallel) |
| Coder Agent | TDD implementation | Design review gate approved |
| Code Review Agent | Internal code review | Implementation complete |
| Security Auditor | Security review (code) | Implementation complete |
| Release Engineer Agent | Safe delivery from merge through production | QA approves PR, PR reaches merge readiness |
| PR Shepherd | PR lifecycle management | PR created |
See ./agents/ directory for detailed agent definitions.
What ships with it
29 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.
- agents/architect-agent.md 13 KB
- agents/code-review-agent.md 15 KB
- agents/coder-agent.md 16 KB
- agents/cto-agent.md 7.4 KB
- agents/customer-service-agent.md 10 KB
- agents/designer-agent.md 10 KB
- agents/issue-orchestrator.md 23 KB
- agents/knowledge-curator-agent.md 9.2 KB
- agents/metrics-agent.md 9.8 KB
- agents/pr-shepherd-agent.md 7.6 KB
- agents/product-manager-agent.md 12 KB
- agents/release-engineer-agent.md 15 KB
- agents/researcher-agent.md 8.2 KB
- agents/security-auditor-agent.md 11 KB
- agents/security-design-agent.md 14 KB
- agents/slack-coordinator-agent.md 5.9 KB
- agents/sre-agent.md 8.7 KB
- agents/swarm-coordinator-agent.md 11 KB
- agents/test-automator-agent.md 11 KB
- guides/agent-coordination.md 14 KB
- references/codex-tools.md 980 B
- references/cursor-tools.md 261 B
- references/opencode-tools.md 331 B
- references/platform-adaptation.md 3.5 KB
- rubrics/adversarial-review-rubric.md 7.3 KB
- rubrics/code-review-rubric.md 12 KB
- rubrics/plan-review-rubric.md 8.0 KB
- rubrics/release-engineering-rubric.md 11 KB
- rubrics/security-review-rubric.md 12 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.
- 1mo ago First seen · 872 lines · 27 tokens per session scan A 2a31dd3e1702
start is a skill published in the GitHub repository dsifry/metaswarm (421 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 7,169 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.