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/vrsen/openswarm/agents-mdgit clone --depth 1 https://github.com/VRSEN/OpenSwarmWhat 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.01053 | $0.01053 |
| Opus 5 | $0.00526 | $0.00526 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
OpenSwarm AGENTS.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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSwarm — Customization Guide
This file gives coding agents (Cursor, Claude Code, Codex, etc.) everything they need to understand and customize this swarm. Read it before making any changes.
What is OpenSwarm?
OpenSwarm is a multi-agent AI team you can fork and reshape into any kind of swarm you need — SEO, sales, research, finance, customer support, or anything else. Each agent is a specialist. They collaborate through a shared orchestrator.
Folder Structure
swarm.py ← main config: imports all agents, defines how they connect
shared_instructions.md ← context shared across every agent
run.py ← CLI entry point (terminal demo)
server.py ← API entry point (FastAPI server)
orchestrator/
orchestrator.py ← agent definition
instructions.md ← system prompt
data_analyst_agent/
data_analyst_agent.py
instructions.md
tools/ ← custom tools for this agent
docs_agent/
docs_agent.py
instructions.md
tools/
slides_agent/
slides_agent.py
instructions.md
tools/
image_generation_agent/
image_generation_agent.py
instructions.md
tools/
video_generation_agent/
video_generation_agent.py
instructions.md
tools/
deep_research/
deep_research.py
instructions.md
tools/
virtual_assistant/
virtual_assistant.py
instructions.md
tools/
shared_tools/ ← tools available to all agents (Composio integrations, etc.)
How Agents Connect (swarm.py)
swarm.py is the only file you need to edit when adding, removing, or rewiring agents. It:
- Imports a
create_*factory function from each agent folder - Instantiates all agents
- Defines communication flows — who can talk to whom
The default pattern is orchestrator-to-all: the orchestrator can send messages to every specialist, and all agents can hand off to each other.
How to Customize
To build your own swarm from this repo:
- Fork and rename the repo (e.g.,
seo-swarm) - Decide which agents to keep, rename, or replace
- Rename the folder and its files to match the new agent's purpose
- Update
instructions.mdwith the new system prompt - Update
swarm.pyto import and register the renamed agent
- Add or remove tools inside each agent's
tools/folder - Update
shared_instructions.mdwith any context all agents should share - Run with
python run.py
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.
- 2d ago First seen · 131 lines · 1,053 tokens per session scan A 71a3168c70d6
OpenSwarm AGENTS.md is an instructions file published in the GitHub repository VRSEN/OpenSwarm (2,855 stars, last pushed 1mo ago), licensed MIT. It adds 1,053 tokens to every session, about $0.0053 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
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
ii-agent AGENTS.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.