Borrowing it
Nothing to install: this file belongs to moonrunnerkc/swarm-orchestrator. 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/moonrunnerkc/swarm-orchestrator/v13-main/CLAUDE.mdgit clone --depth 1 https://github.com/moonrunnerkc/swarm-orchestratorWrote 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/moonrunnerkc/swarm-orchestrator/claude-md)<a href="https://agentmods.dev/instructions/moonrunnerkc/swarm-orchestrator/claude-md"><img src="https://agentmods.dev/badge/instructions/moonrunnerkc/swarm-orchestrator/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.05266 | $0.05266 |
| Opus 5 | $0.02633 | $0.02633 |
| Sonnet 5 | $0.01053 | $0.01053 |
| Haiku 4.5 | $0.00527 | $0.00527 |
Grade A, and why
swarm-orchestrator CLAUDE.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 yesterday.
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.
This is a copy
100% identical to swarm-orchestrator AGENTS.md — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Swarm Orchestrator v13: an evidence-first coding agent. Every claim of completed work must resolve to machine-captured evidence in a tamper-evident ledger. Quality gates run and auto-resolve under a ratchet. Local model selection is measured, never guessed. Full rationale lives in docs/build-guide.md; read it before structural work.
Commands
npm run typecheck: tsc, strict, no emitnpm run lint: Biome checknpm run format: Biome format, writenpm test: Vitest, full suitenpm run gates: all of the above in sequence; this is the definition of greennpm run dev: run the CLI from source against a scratch workspace
Run npm run gates before claiming any task complete. Paste the real output. Never summarize gate results from memory.
Architecture Map
src/agent-run.ts: one task start to finish (policy guard, tools, chokepoint, loop, gates). The CLI and every parallel worker call this same function; a worker differs in its directory, its chain, and one optional tool, the peer trail, which the single-agent path is never offered and which leaves its prompt byte-identical.src/core: agent loop. Plan, act, verify. All stochastic inputs (clock, random, model) injected via interfaces, never imported directly.src/tools: read, write, edit, shell, search, list. Every call goes through the chokepoint insrc/tools/chokepoint.ts: ledger record, provenance tag, policy-guard enforcement. No tool may bypass it. The guard is a lexical path and program policy, not a sandbox: what a run actually executes under is measured by the containment self-test insrc/execand recorded as an execution-envelope record.src/exec: process execution shared by tools and gates: the environment a child is given (built, never inherited), the process-group lifecycle that stops what a command started, the containment self-test that decides a run's execution mode, and the container backend that mode can be earned against. Imported bysrc/toolsandsrc/gates; imports neither.src/evidence: append-only JSONL ledger, hash chain, content-addressed blob store, evidence DAG, bundle export, embedded verifier, HTML review renderer.src/gates: gate definitions as data, runner, auto-resolve loop with ratchet, escalation.src/providers: the only module allowed to import the Vercel AI SDK. Frontier plus OpenAI-compatible local (Ollama, rapid-mlx). Local endpoint discovery.src/select: hardware probe, static shortlist fit, calibration micro-eval, bandit reward log.src/workers: phase 6 scale-out. Git worktree per worker, each running the ordinary loop fromsrc/agent-run.ts, and a merge queue that lands them sequentially under the ratchet. Nothing here is imported by the single-agent path.src/tui: Ink single-screen UI. Renders exclusively from ledger projections.src/config: Zod-validated swarm.toml, zero-config defaults.
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.
- yesterday Changed · +1 lines · +356 tokens per session 21000c6b3c9d
- 4d ago Changed · +2 lines · +320 tokens per session 2da03f7b0d80
- 8d ago First seen · 68 lines · 4,590 tokens per session scan E 9742d1c0cc28
swarm-orchestrator CLAUDE.md is an instructions file published in the GitHub repository moonrunnerkc/swarm-orchestrator (106 stars, last pushed today), licensed ISC. It adds 5,266 tokens to every session, about $0.0263 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to swarm-orchestrator AGENTS.md, differing in 1 line, and is treated as a copy.
Other instructions, from other repositories
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).
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.
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).
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.