agent-coordination-discipline

agent-coordination-discipline is a skill for Claude Code from MadAppGang/claude-code. It costs 42 tokens per session (3,512 once invoked), scanned A, original, MIT.

A guide for deciding when to delegate work to another coding agent and how to coordinate one or more agents.

In plain words
What is it for?
It helps choose an agent, define an independent task, select an external model when needed, and coordinate parallel agent work.
Why use it?
It reduces unnecessary delegation, unclear responsibilities, isolated work that cannot be combined, and agent tasks with no clear definition of success.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dev plugin — 47 skills, 12 commands, 14 agents shipped together

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.

agentmods
npx agentmods add skills/madappgang/claude-code/agent-coordination-discipline
Any agent
npx skills add MadAppGang/claude-code --skill agent-coordination-discipline
Clone the repo
git clone --depth 1 https://github.com/MadAppGang/claude-code

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 47 skills, 12 commands, 14 agents.

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 agent-coordination-discipline

README.md
[![agentmods](https://agentmods.dev/badge/skills/madappgang/claude-code/agent-coordination-discipline.svg)](https://agentmods.dev/skills/madappgang/claude-code/agent-coordination-discipline)
Your own site
<a href="https://agentmods.dev/skills/madappgang/claude-code/agent-coordination-discipline"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/agent-coordination-discipline.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,512 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00042 $0.03512
Opus 5 $0.00021 $0.01756
Sonnet 5 $0.00008 $0.00702
Haiku 4.5 $0.00004 $0.00351

Measured 3d ago against content hash 0f11b0255a56, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

agent-coordination-discipline 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 3d 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.

plugins/dev/skills/discipline/agent-coordination-discipline/SKILL.md · 432 lines

How it starts

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

Agent Coordination Discipline

Iron Law: "NO AGENT LAUNCH WITHOUT CLEAR DELEGATION CRITERIA"

When to Use

Use this skill when:

  • Considering launching an agent with the Task tool
  • Evaluating whether a task requires agent delegation
  • Selecting between different agent types or external models
  • Coordinating multiple agents in a workflow
  • Implementing external-model for external model delegation
  • Debugging agent coordination failures

This skill prevents premature agent launches, redundant agent usage, and poor task isolation that wastes thinking budget and causes coordination failures.

Red Flags (Violation Indicators)

  • Agent for single grep - Launching agent to run one grep/glob command (trivial-task anti-pattern)
  • Missing external-model model - Using external-model without explicit model name specification
  • No task isolation - Agent task description lacks independent context or success criteria
  • No success criteria - Task description doesn't define what "done" looks like
  • Default thinking pattern - Not considering whether task needs deep thinking vs. fast execution
  • Multiple agents without coordination - Launching 2+ agents without clear result routing plan
  • Result not used - Launching agent but not routing/validating its output
  • Agent for trivial decision - Using agent to make decision you could make directly
  • No tool exhaustion check - Launching agent before trying native tools first
  • Missing timeout consideration - Not evaluating if task needs extended thinking time
  • No error handling plan - Not defining what happens if agent fails or returns partial results
  • Skill gap unclear - Not identifying what specific expertise the agent provides

Key Concepts

1. Agent vs. Native Tools Decision Tree

Does the task require:
├─ Single tool call (grep, read, edit)?
│  └─ ✗ NO AGENT - Use native tool directly
├─ 2-3 sequential tool calls?
│  └─ ✗ NO AGENT - Use tools directly in sequence
├─ Multi-step investigation with branching logic?
│  └─ ✓ AGENT - Task tool with developer/architect agent
├─ External model expertise (Grok, DeepSeek, etc.)?
│  └─ ✓ AGENT - external-model pattern with model specification
├─ Parallel exploration of multiple code paths?
│  └─ ✓ AGENT - Multiple Task calls with coordination
└─ High-risk change needing isolation?
   └─ ✓ AGENT - Task tool with sandbox/review focus

Read the full file on GitHub · 432 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. 3d ago First seen · 432 lines · 42 tokens per session scan A 0f11b0255a56

Subscribe to this mod's changes

agent-coordination-discipline is a skill published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 3,512 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-09-03.

Related

Other skills, from other repositories

sparc-methodology

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.

ruvnet/RuView · 29 tokens

agent-framework-py-release

Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…

microsoft/agent-framework · 103 tokens

foundry-hosted-agent-validation

Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.

microsoft/agent-framework · 82 tokens

build-and-test

How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.

microsoft/agent-framework · 26 tokens

python-feature-lifecycle

Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.

microsoft/agent-framework · 43 tokens

python-code-quality

Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.

microsoft/agent-framework · 40 tokens