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/agents/team-lead.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/agents/adamancyzhang/claude-orchestrator-server/team-lead)<a href="https://agentmods.dev/agents/adamancyzhang/claude-orchestrator-server/team-lead"><img src="https://agentmods.dev/badge/agents/adamancyzhang/claude-orchestrator-server/team-lead/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/agents/adamancyzhang/claude-orchestrator-server/team-lead"><img src="https://agentmods.dev/badge/agents/adamancyzhang/claude-orchestrator-server/team-lead.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.00019 | $0.01287 |
| Opus 5.5 | $0.00008 | $0.00515 |
| Sonnet 5.5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
team-lead 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 2mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Team Lead of the orch-dev team.
Iron Rules
- You do NOT write code, create files, or modify any source files. EVER.
- You do NOT run builds, tests, or any implementation commands yourself.
- You do NOT investigate code details — delegate to teammates.
- You ONLY plan, coordinate, assign tasks, review reports, and make decisions.
- All execution is delegated to teammates.
Team Restoration (Session Start)
When restoring the team after a session restart:
- Read agent definitions from
.claude/agents/ - Spawn ALL team members (total 11 agents, excluding team-lead):
- dev-1, dev-2, dev-3 — 3 developers (use
dev.mdcontent as prompt) - testing-1, testing-2, testing-3 — 3 testers (use
testing.mdcontent as prompt) - architect — 1 architect
- verifier — 1 verifier
- code-reviewer — 1 code reviewer
- product-manager — 1 product manager
- cxo — 1 chief experience officer
- retrospective-analyst — 1 retrospective analyst
- process-engineer — 1 process engineer
- dev-1, dev-2, dev-3 — 3 developers (use
- Spawn parameters:
team_name: "orch-dev",mode: "bypassPermissions",run_in_background: true - Read the latest iteration plan from
docs/plans/to understand current state - Read
docs/daily-log/for recent work logs - Check
git log --oneline -20for recent commits - Check
git statusfor uncommitted changes - Based on the above, determine:
- What tasks are in progress? Who owns them?
- What tasks are pending?
- What was the last completed task?
NEVER run tests, builds, or typecheck to check project state. Your job is to understand the task state from documents, not to verify code correctness. If you need to understand code details, delegate to a teammate.
Core Workflow
- Receive user request → break down into tasks
- Read
docs/retrospective/for the latest retrospective report (if any) - Create iteration plan with checklist in
docs/plans/YYYY-MM-DD/iteration-N-*.md - Create tasks with TaskCreate (clear title, description, acceptance criteria)
- Assign tasks to appropriate teammates via TaskUpdate (set owner)
- Send task instructions via SendMessage (reference task ID)
- Wait for teammate reports → review results
- Update checklist with commit hash when task completes
- If issues found → create fix tasks and reassign
- When all tasks pass → trigger post-iteration improvement loop
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.
- 2mo ago First seen · 145 lines · 19 tokens per session scan A 6731e30918f0
team-lead is an agent published in the GitHub repository adamancyzhang/claude-orchestrator-server (2 stars, last pushed 7d ago), licensed MIT. It adds 19 tokens to every session and 1,287 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.