Borrowing it
Nothing to install: this file belongs to tlangridge/agent-swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tlangridge/agent-swarm/master/CLAUDE.mdgit clone --depth 1 https://github.com/tlangridge/agent-swarmWrote 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/tlangridge/agent-swarm/claude-md)<a href="https://agentmods.dev/instructions/tlangridge/agent-swarm/claude-md"><img src="https://agentmods.dev/badge/instructions/tlangridge/agent-swarm/claude-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.1 | $0.00585 | $0.00585 |
| Opus 5 | $0.00293 | $0.00293 |
| Sonnet 5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
agent-swarm CLAUDE.md scanned grade A 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Agents communicate via REST API at `/api/swarm/*` — all agents use `curl` to send/receive messages How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Swarm
Security — Open Source Repo
This is a public open-source repository. Before every commit:
- Check
.gitignore— Ensure.env,data/agents/,data/docker/, and any files containing secrets are gitignored. - Never commit API keys, tokens, or credentials — All secrets belong in
.env(which is gitignored). If you see a key in source code, move it to.envand reference viaprocess.env. - Never commit agent identity data — The
data/directory contains per-agent JSON files and Docker volume state. It must stay gitignored. - Audit new files — When creating new files, consider whether they could contain sensitive data. When in doubt, add to
.gitignore.
Project Structure
server/— Express + WebSocket + node-pty backend (TypeScript, runs via tsx)server/services/swarm-registry.ts— In-memory swarm membership and role managementserver/services/swarm-prompts.ts— System prompt templates for agent swarm awarenessserver/routes/swarm.ts— REST API for agent-to-agent messaging (/api/swarm/*)
client/— React + Vite frontend (xterm.js terminals, react-mosaic tiling)docker/— Dockerfile for sandboxed agent containersdata/— Runtime data (agents JSON, Docker volumes) — gitignored
Dev Commands
npm run dev— Start server + client concurrentlydocker build -t agent-swarm-sandbox docker/— Build the sandbox image
Swarm Coordination
- Agents communicate via REST API at
/api/swarm/*— all agents usecurlto send/receive messages - Messages are injected into agent terminals via
session.pty.write()with[SWARM from <name>]:framing - Agents authenticate with
X-Session-Idheader (session ID passed viaAGENT_SWARM_SESSION_IDenv var) - Single lead agent at a time — user designates at launch or toggles via crown icon in tile toolbar
- Claude Code agents get full swarm instructions via
--append-system-prompt - Non-Claude agents (Gemini, Codex, Bash) get env vars + a one-time terminal-injected orientation message
- Docker agents reach the host API via
http://host.docker.internal:${PORT}
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.
- 6d ago First seen · 42 lines · 585 tokens per session scan A 9fa97863af6f
agent-swarm CLAUDE.md is an instructions file published in the GitHub repository tlangridge/agent-swarm (5 stars, last pushed 6mo ago), licensed MIT. It adds 585 tokens to every session, about $0.0029 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.