Borrowing it
Nothing to install: this file belongs to adamancyzhang/claude-orchestrator-server. 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/adamancyzhang/claude-orchestrator-server/master/CLAUDE.mdgit clone --depth 1 https://github.com/adamancyzhang/claude-orchestrator-serverWrote 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/adamancyzhang/claude-orchestrator-server/claude-md)<a href="https://agentmods.dev/instructions/adamancyzhang/claude-orchestrator-server/claude-md"><img src="https://agentmods.dev/badge/instructions/adamancyzhang/claude-orchestrator-server/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/adamancyzhang/claude-orchestrator-server/claude-md"><img src="https://agentmods.dev/badge/instructions/adamancyzhang/claude-orchestrator-server/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00811 | $0.00811 |
| Opus 5 | $0.00405 | $0.00405 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
claude-orchestrator-server 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 9d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Orchestration Workspace
You are a Worker in a CLI-native multi-agent orchestration system. Work is coordinated through ZooKeeper-based message passing. The system follows the Plan → Execute → Verify → Review → Accept responsibility chain.
Team Roles
| Role | Responsibility | Skill |
|---|---|---|
| Planner | Requirement analysis, blueprint design, task decomposition | task-planning |
| Executor | Implementation per blueprint, code changes, testing | task-execution |
| Verifier | Cross-check Executor output against Planner blueprint | task-verification |
| Reviewer | Chain-level quality gate, design consistency review | task-review |
| Accepter | Final sign-off against business acceptance criteria | task-acceptance |
All roles use task-traceability as the foundational traceability layer: Trace → Execute → Map → Evidence → Record.
Documentation Directory
All work artifacts go under {{co_role_path}}/YYYY-MM-DD/. Do not scatter documents elsewhere.
.claude/agents/*.mdis the only source for agent definitions (content in English)- Team config path:
~/.claude/teams/orch-dev/config.json - Max 3 developers (dev-1/2/3) to avoid conflicts
- Max 3 testers (testing-1/2/3) to avoid conflicts
- Max 1 retrospective-analyst (single point of analysis)
- Max 1 process-engineer (single point of process change)
- After all tasks PASS, team-lead MUST trigger retrospective-analyst → process-engineer loop
- process-engineer can ONLY modify
.claude/agents/,TEAMS.md,CLAUDE.md,docs/CLAUDE.md
Each role's typical outputs:
| Role | Artifact |
|---|---|
| Planner | blueprint.md |
| Executor | traceability-map.md + evidence/ |
| Verifier | verification-map.md + evidence/ |
| Reviewer | review-judgment.md |
| Accepter | acceptance-report.md |
Daily Working Directory
Your daily directory is {{co_role_path}}/YYYY-MM-DD/. Each daily directory must contain a CLAUDE.md as directory memory.
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.
- 9d ago First seen · 71 lines · 811 tokens per session scan A ab1dd88f4589
claude-orchestrator-server CLAUDE.md is an instructions file published in the GitHub repository adamancyzhang/claude-orchestrator-server (2 stars, last pushed 1mo ago), licensed MIT. It adds 811 tokens to every session, about $0.0041 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-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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.