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 instructions/dsifry/metaswarm/gemini-mdgit 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/instructions/dsifry/metaswarm/gemini-md)<a href="https://agentmods.dev/instructions/dsifry/metaswarm/gemini-md"><img src="https://agentmods.dev/badge/instructions/dsifry/metaswarm/gemini-md.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.00548 | $0.00548 |
| Opus 5 | $0.00274 | $0.00274 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
metaswarm GEMINI.md 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 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.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
metaswarm
Multi-agent orchestration framework for software development. 18 specialized agents, 14 skills, quality gates, TDD enforcement.
Getting Started
Run /metaswarm:start-task to begin tracked work, or /metaswarm:setup to configure metaswarm for this project.
Available Commands
| Command | Purpose |
|---|---|
/metaswarm:start-task |
Begin tracked work on a task |
/metaswarm:prime |
Load relevant knowledge before starting |
/metaswarm:review-design |
Trigger design review gate (5 reviewers) |
/metaswarm:pr-shepherd |
Monitor a PR through to merge |
/metaswarm:self-reflect |
Extract learnings after a PR merge |
/metaswarm:handle-pr-comments |
Handle PR review comments |
/metaswarm:brainstorm |
Refine an idea before implementation |
/metaswarm:create-issue |
Create a well-structured GitHub Issue |
/metaswarm:external-tools-health |
Check status of external AI tools |
/metaswarm:setup |
Interactive guided setup |
/metaswarm:status |
Run diagnostic checks |
Workflow
For complex features, describe what you want with a Definition of Done and say:
Use the full metaswarm orchestration workflow.
This runs: Research -> Plan -> Design Review Gate -> Work Unit Decomposition -> Orchestrated Execution (4-phase loop per unit) -> Final Review -> PR.
Quality Gates (MANDATORY)
- After brainstorming -> MUST run
/metaswarm:review-designbefore planning - After any plan -> MUST run Plan Review Gate before presenting to user
- Before finishing branch -> MUST run
/metaswarm:self-reflectbefore PR - Coverage ->
.coverage-thresholds.jsonis the single source of truth. BLOCKING gate. - TDD is mandatory -> Write tests first, watch them fail, then implement
Rules
- NEVER use
--no-verifyon git commits - NEVER use
git push --forcewithout explicit user approval - ALWAYS follow TDD
- STAY within declared file scope
Platform Notes
Gemini CLI has limited sub-agent support. When sub-agents are unavailable:
- Design review runs sequentially (each reviewer in-session one at a time)
- Adversarial review uses rubrics as structured checklists
- Quality of review is maintained through rubric structure
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 · 55 lines · 548 tokens per session scan A 29367cfa05ef
metaswarm GEMINI.md is an instructions file published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It adds 548 tokens to every session, about $0.0027 per session on Opus 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.