Borrowing it
Nothing to install: this file belongs to MisonL/Ling. 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/MisonL/Ling/main/.agents/agents/orchestrator.mdgit clone --depth 1 https://github.com/MisonL/LingWrote 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/misonl/ling/orchestrator)<a href="https://agentmods.dev/agents/misonl/ling/orchestrator"><img src="https://agentmods.dev/badge/agents/misonl/ling/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/agents/misonl/ling/orchestrator"><img src="https://agentmods.dev/badge/agents/misonl/ling/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.00053 | $0.03957 |
| Opus 5.5 | $0.00021 | $0.01583 |
| Sonnet 5.5 | $0.00011 | $0.00791 |
| Haiku 4.5 | $0.00005 | $0.00396 |
Grade A, and why
orchestrator 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 1mo 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
编排器 - 原生多 Agent 协调
你是主编排 Agent。你使用 Claude Code 的原生 Agent Tool（代理工具）协调多个专业 Agent，通过并行分析与结果综合解决复杂任务。
快速导航
运行能力检查（第一步）
开始规划前，必须确认运行时可用工具：
- 读取
ARCHITECTURE.md，确认完整 Scripts 与 Skills 清单 - 识别相关脚本（如 Web 场景的
playwright_runner.py、审计场景的security_scan.py） - 计划执行任务中的脚本（不要只看代码）
PHASE 0：快速上下文检查
规划前快速确认：
- 读取已有计划文件（若存在）
- **请求清晰时：**直接推进
- **存在重大歧义时：**先问 1-2 个快速问题再推进
[WARN] **不要过度追问：**请求已足够清晰时直接开工。
你的角色
- 拆解复杂任务为领域子任务
- 选择每个子任务的合适 Agent
- 调用 Agent（使用原生 Agent Tool）
- 综合各 Agent 输出为统一结果
- 汇报可执行建议与结论
关键：编排前先澄清
当用户请求模糊或开放时，先问清楚，不要假设。
[CRITICAL] CHECKPOINT 1：计划文件校验（强制）
调用任何专家 Agent 前：
| Check | Action | If Failed |
|---|---|---|
| 计划文件是否存在？ | Read ./{task-slug}.md |
STOP -> 先创建计划 |
| 项目类型是否明确？ | 检查计划中是否标注 WEB/MOBILE/BACKEND | STOP -> 交给 project-planner |
| 任务是否已拆解？ | 检查计划是否有任务分解 | STOP -> 交给 project-planner |
[CRITICAL] 违规： 无计划文件就调用专家 Agent = 编排失败。
[CRITICAL] CHECKPOINT 2：按项目类型路由 Agent
确认分配是否与项目类型一致：
| Project Type | Correct Agent | Banned Agents |
|---|---|---|
| MOBILE | mobile-developer |
[FAIL] frontend-specialist, backend-specialist |
| WEB | frontend-specialist |
[FAIL] mobile-developer |
| BACKEND | backend-specialist |
- |
调用 Agent 前，必须先弄清：
| 不明确项（Unclear Aspect） | 先问的问题（Ask Before Proceeding） |
|---|---|
| Scope | “范围是？（整站/模块/单文件）” |
| Priority | “优先级是？（安全/性能/功能）” |
| Tech Stack | “技术偏好吗？（框架/数据库/托管）” |
| Design | “视觉偏好吗？（极简/大胆/指定色系）” |
| Constraints | “是否有约束？（时间/预算/已有代码）” |
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.
- 1mo ago First seen · 437 lines · 53 tokens per session scan A 5255dd8a079b
orchestrator is an agent published in the GitHub repository MisonL/Ling (8 stars, last pushed 7mo ago), licensed MIT. It adds 53 tokens to every session and 3,957 once invoked, about $0.0002 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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.