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 skills add adamancyzhang/claude-orchestrator-server --skill claude-orchestratorgit 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/skills/adamancyzhang/claude-orchestrator-server/claude-orchestrator)<a href="https://agentmods.dev/skills/adamancyzhang/claude-orchestrator-server/claude-orchestrator"><img src="https://agentmods.dev/badge/skills/adamancyzhang/claude-orchestrator-server/claude-orchestrator/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/skills/adamancyzhang/claude-orchestrator-server/claude-orchestrator"><img src="https://agentmods.dev/badge/skills/adamancyzhang/claude-orchestrator-server/claude-orchestrator.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.00091 | $0.01486 |
| Opus 5 | $0.00046 | $0.00743 |
| Sonnet 5 | $0.00018 | $0.00297 |
| Haiku 4.5 | $0.00009 | $0.00149 |
Grade A, and why
claude-orchestrator 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 11d 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.
3. **Vague completion criteria** — "Works correctly" is not verifiable. Use specific commands and expected outputs (e.g., "curl -X POST /api/login returns 201 with a valid JWT in the response body"). How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Orchestrator — Worker Reference
You are a Worker in a multi-agent orchestration system. Your work is coordinated through ZooKeeper. The system follows the Plan → Build → Verify → Review → Accept responsibility chain. This reference helps you stay on track.
Quick Orientation
When you start working, locate these files:
| File | Purpose | Read When |
|---|---|---|
CLAUDE.md (worktree root) |
Team rules, directory structure, chain overview | Every session start |
.claude-orchestrator/docs/{your_name}/CLAUDE.md |
Your role-specific rules and output standards | Every session start |
.claude-orchestrator/docs/{your_name}/YYYY-MM-DD/CLAUDE.md |
Today's session memory | Every session start (create if missing) |
.claude/skills/task-traceability/SKILL.md |
Foundation: Trace → Execute → Map → Evidence → Record | Every task |
.claude/skills/{your_link_skill}/SKILL.md |
Your link-specific process | When starting your link |
Directory Memory Rules (Non-Negotiable)
- All your output goes under
.claude-orchestrator/docs/{your_name}/YYYY-MM-DD/(use today's date) - Every daily directory must have a
CLAUDE.md— update it after each completed sub-task - Read upstream artifacts from their docs directories before starting your link
- Write your artifact to the docs directory so the next Worker can find it
Artifact Names by Link
| Your Link | Your Output File | Who Reads It |
|---|---|---|
| plan | blueprint.md |
Builder, Verifier, Reviewer, Accepter |
| build | traceability-map.md + evidence/ |
Verifier, Reviewer, Accepter |
| verify | verification-map.md + evidence/ |
Reviewer, Accepter |
| review | review-judgment.md |
Accepter |
| accept | acceptance-report.md |
(chain closes) |
Responsibility Chain Rules
Every Link Must
- Trace — Read upstream artifacts before starting. If missing → BLOCKED, report to Leader.
- Execute — Follow the standard process in your skill file.
- Map — Link every output to a specific upstream requirement.
- Evidence — Provide verifiable proof (not claims) for every output.
- Record — Write to BOTH
{{result_path}}(for Leader) AND.claude-orchestrator/docs/{your_name}/YYYY-MM-DD/{artifact}.md(for downstream).
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.
- 11d ago First seen · 103 lines · 91 tokens per session scan A b010104db4dc
claude-orchestrator is a skill published in the GitHub repository adamancyzhang/claude-orchestrator-server (2 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 1,486 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…