agentmods.dev

coordinate-team

coordinate-team is a skill for Claude Code from Mr-Nothing-L/awesome-agent-team. It costs 101 tokens per session (671 once invoked), scanned A, original, MIT.

A coordination guide for an Agent Team that is already running. It explains how to monitor agents, resolve blocked work, and combine their completed results.

In plain words
What is it for?
Use it to check team progress, nudge stuck agents, resolve blockers, verify the final results, and disband the team when finished.
Why use it?
It helps keep a multi-agent project moving when members stall or need direction. It also provides a closing process and preserves the team’s planning and result files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the awesome-agent-team plugin — 5 skills, 1 command, 1 agent shipped together

not rated 2repo 4mo ago A scan 101 tokens original MIT

Good fit Use it to check team progress, nudge stuck agents, resolve blockers, verify the final results, and disband the team when finished.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mr-nothing-l/awesome-agent-team/coordinate-team
View source ↗ Mr-Nothing-L/awesome-agent-team
Install

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.

Any agent
npx skills add Mr-Nothing-L/awesome-agent-team --skill coordinate-team
Clone the repo
git clone --depth 1 https://github.com/Mr-Nothing-L/awesome-agent-team

Made for: Claude Code.

Or install awesome-agent-team, the plugin that ships this one along with the rest of its 5 skills, 1 command, 1 agent.

Wrote 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.

agentmods badge for coordinate-team

README.md
[![agentmods](https://agentmods.dev/badge/skills/mr-nothing-l/awesome-agent-team/coordinate-team/github.svg)](https://agentmods.dev/skills/mr-nothing-l/awesome-agent-team/coordinate-team)
Your own site
<a href="https://agentmods.dev/skills/mr-nothing-l/awesome-agent-team/coordinate-team"><img src="https://agentmods.dev/badge/skills/mr-nothing-l/awesome-agent-team/coordinate-team/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.

agentmods 80×15 button for coordinate-team

Your own site · 80×15
<a href="https://agentmods.dev/skills/mr-nothing-l/awesome-agent-team/coordinate-team"><img src="https://agentmods.dev/badge/skills/mr-nothing-l/awesome-agent-team/coordinate-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 671 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00101 $0.00671
Opus 5 $0.00051 $0.00336
Sonnet 5 $0.00020 $0.00134
Haiku 4.5 $0.00010 $0.00067

Measured 10d ago against content hash 9e569fba45b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

coordinate-team 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 10d 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.

skills/coordinate-team/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

coordinate-team

Language matching: detect the language the user is writing in and respond in the same language. If the user writes in Chinese, reply in Chinese. If English, reply in English. Do not mix languages unless the user does.

Keep a running Agent Team on track and deliver results.

When to use this skill

  • A team is already running (spawned via spawn-team or /start-team)
  • You want to check progress, resolve blockers, or nudge stalled teammates
  • Work is wrapping up and you need a final summary

What the main session does

While the team runs:

  • Cycle through teammates with Shift+Up/Down (in-process) or pane-click (split mode).
  • Watch the shared task list (Ctrl+T).
  • Nudge stuck teammates via SendMessage.

When work is complete:

  1. Read ./team-results.md (written by the Team-Leader). Verify against the original mission in ./recruitment-plan.md.
  2. Summarize for the user (short — they read the diff and the results file).
  3. Call TeamDelete to disband the team.
  4. Leave artifacts in place: ./.claude/agents/, ./recruitment-plan.md, ./team-results.md. The user may commit them so future /start-team runs in this repo start from a richer baseline.

What the Team-Leader does (as a teammate)

The Team-Leader coordinates execution. They should:

  1. Read ./recruitment-plan.md to remember the plan (subagent context does not carry over across respawns).
  2. Create initial tasks via TaskCreate from the Work Plan section. Use addBlockedBy to encode dependencies.
  3. Brief each teammate with SendMessage. Mention their first task and who they should coordinate with.
  4. Monitor via TaskList. Re-assign blocked work. Resolve cross-team blockers.
  5. Synthesize results when work completes. Write a final summary to ./team-results.md and notify the main lead.

Keep messages concise. Every message costs tokens.

User interaction model

The user can:

  • Talk to any teammate directly via the UI (pane-click or Shift+Up/Down)
  • Ask the main session to nudge a teammate via SendMessage
  • Ask the main session to stop a task via TaskStop
  • Ask the main session to disband the team via TeamDelete

Read the full file on GitHub · 62 lines

Changes

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.

  1. 10d ago First seen · 62 lines · 101 tokens per session scan A 9e569fba45b2

Subscribe to this mod's changes

coordinate-team is a skill published in the GitHub repository Mr-Nothing-L/awesome-agent-team (2 stars, last pushed 4mo ago), licensed MIT. It adds 101 tokens to every session and 671 once invoked, about $0.0005 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.

Building agentsProject management
Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens