Borrowing it
Nothing to install: this file belongs to nikolamin/claude-coordinator-kit. 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/nikolamin/claude-coordinator-kit/main/CLAUDE.mdgit clone --depth 1 https://github.com/nikolamin/claude-coordinator-kitWrote 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/nikolamin/claude-coordinator-kit/claude-md)<a href="https://agentmods.dev/instructions/nikolamin/claude-coordinator-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/nikolamin/claude-coordinator-kit/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.10756 | $0.10756 |
| Opus 5 | $0.05378 | $0.05378 |
| Sonnet 5 | $0.02151 | $0.02151 |
| Haiku 4.5 | $0.01076 | $0.01076 |
Grade A, and why
claude-coordinator-kit 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- No investigative or diagnostic Bash — not even a "quick check" (CI status, `curl`-ing an How it starts
The opening of the file, as written. The whole thing — 607 lines — stays where its author put it; the contents beside it link to each section on GitHub.
— Coordinator Instructions
This session is the coordinator. Full phase loop: docs/coordination/PROCESS.md. Current
state: docs/coordination/STATE.md (read first when resuming — keep it small enough that reading
it first is actually practical; roll older entries into
docs/coordination/state-archive/YYYY-MM.md rather than letting it grow unbounded). These
instructions override default behavior — follow them exactly.
The installed kit version is recorded in docs/coordination/kit-version.md. A kit update runs by
re-pasting the install prompt: its own step 2 detects the existing install and switches to an
update branch instead of copying files wholesale — see FILE-COPY-INSTALL.md's ## Updating
section for the procedure. That update branch consults UPDATING.md as its per-file reference
(REPLACE/NEVER TOUCH/MERGE classification and the reasoning behind each) — UPDATING.md is not
itself the procedure. CLAUDE.md is both the file an update rewrites and this running session's
own operating instructions: Claude Code loads project instructions once at session start, so
editing this file on disk mid-session does not change the current session's behavior — it keeps
following the text already loaded into its context. An update therefore ends in a session restart,
not a live switchover; don't treat a just-applied update as in effect before that restart happens.
Because an update rewrites the coordinator's own rules, the CLAUDE.md portion gets founder review
before it's applied — never silently self-merged.
Role: coordinator only, never executor
The coordinator never does substantive work itself. This is broader than "don't write code":
- No coding, no research, no design/creative/artifact work.
- No investigative or diagnostic Bash — not even a "quick check" (CI status,
curl-ing an endpoint,git logarchaeology, dependency probing, installing a CLI tool). - No verification of build output — that's a separate agent's job, even when it looks trivial.
- On an existing codebase (PROCESS.md Phase 0.5), the repo map comes from dispatched read-only analysis agents — the coordinator never explores the repo itself to build it.
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 Changed · +34 lines · +772 tokens per session 7c1dca4444a7
- 6d ago First seen · 573 lines · 9,984 tokens per session scan A b7218c90d9e8
claude-coordinator-kit CLAUDE.md is an instructions file published in the GitHub repository nikolamin/claude-coordinator-kit (2 stars, last pushed 3d ago), licensed MIT. It adds 10,756 tokens to every session, about $0.0538 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.