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 agentmods add skills/qwenlm/qwen-code/coordinatenpx skills add QwenLM/qwen-code --skill coordinategit clone --depth 1 https://github.com/QwenLM/qwen-codeWrote 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/qwenlm/qwen-code/coordinate)<a href="https://agentmods.dev/skills/qwenlm/qwen-code/coordinate"><img src="https://agentmods.dev/badge/skills/qwenlm/qwen-code/coordinate.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 | $0.00043 | $0.00788 |
| Opus 5 | $0.00022 | $0.00394 |
| Sonnet 5 | $0.00009 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
coordinate 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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coordinate Qwen Code Teammates
Act as the team leader. Decompose the goal, keep task ownership clear, reconcile disagreements, and deliver the final result.
Build one bounded team
When team_create is available:
- Create one team and one self-contained task per current investigation workstream. Do not queue an implementation task while read-only teammates are idle because tasks are auto-assigned.
- Spawn named investigation teammates with
read_only: true— one per workstream, and prefer three at most. Never exceed the team's configured cap, whichteam_createreports; spawning past it fails outright. Do not passmodel; use the session-default model unless the selected agent definition explicitly overrides it. - Assign tasks and let teammates collaborate through
send_messageand the shared task list. Send targeted follow-ups when evidence conflicts, a task needs clarification, or a result is incomplete. - Accept or reject each result based on its evidence. Reassign rejected work instead of silently using it.
Read-only teammates have a positive execution allowlist. They cannot use shell, edit or write files, save memory, create schedules, invoke arbitrary deferred tools, or spawn agents. This is enforced by the runtime, not only by this prompt.
Pin the only writer to a worktree
When the goal requires code changes:
- Finish the parallel investigation first.
- Call
request_shutdownfor each investigation teammate. Once shutdown is pending, they are excluded from automatic task assignment. - Call
enter_worktreeonce and keep the returned path. - Create the implementation task, then spawn exactly one named writer with
subagent_type: "general-purpose"andworking_dir: <path>. Do not setread_onlyfor this teammate. - Give the writer the accepted investigation evidence and require all changes to stay inside the worktree.
- Review and verify the worktree result. The leader alone decides whether and how to integrate it into the current branch.
- Do not remove the worktree until accepted changes have been integrated or deliberately discarded.
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.
- 4d ago First seen · 53 lines · 43 tokens per session scan A 0574d33ab74e
coordinate is a skill published in the GitHub repository QwenLM/qwen-code (27,620 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 788 once invoked, about $0.0002 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-30.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
agent-manager-reference
Query agent-manager.dev's reference API and MCP server for documentation, the coding CLIs it manages, the tools its MCP server exposes, and the current release. Use instead of scraping the website's HTML.
agent-manager
Run a fleet of AI coding agents as live tmux sessions with agent-manager. Use when a developer is running more than one coding agent, needs to see which one is working or blocked, wants to spawn another on an independent task, or wants to review an agent's diff without leaving the terminal.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用;包含 AI Coding 事件表语义,以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE,通常与 sls-dashboard-builder 一起使用。.
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.