Agent skill

Agent Coordination Discipline

by MadAppGang in MadAppGang/claude-code

A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

MITAuto-check passedAgent Workflows

Install Agent Coordination Discipline

skills CLI
$ npx skills add MadAppGang/claude-code --skill agent-coordination-discipline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MadAppGang/claude-code agent-coordination-discipline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/dev/skills/discipline/agent-coordination-discipline .claude/skills/agent-coordination-discipline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-coordination-discipline
GitHub stars
285
Token cost
~3.8k tokens
SKILL.md length
1,018 words
Files
1
Skills in repo
69
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

  • Works in 7 steps: Agent vs. Native Tools Decision Tree → Task Isolation Requirements → External Model Pattern → …
  • Deciding whether to launch an agent
  • SKILL.md covers When to Use, Red Flags (Violation Indicators), Key Concepts and When to Use Agents, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Coordination Discipline is an agent skill from MadAppGang/claude-code. Use when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents. Covers delegation criteria, external-model patterns, task isolation, and agent selection strategies.

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: claude code plugins marketplace. The licence is MIT.

When your agent uses it

  • Deciding whether to launch an agent
  • Selecting which agent to use
  • Coordinating multiple agents

Example prompts

  • “/agent-coordination-discipline”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Agent vs. Native Tools Decision Tree
  2. Task Isolation Requirements
  3. External Model Pattern
  4. Model Selection
  5. Context Packaging
  6. Success Criteria Definition
  7. Result Routing

What it can do on your machine

Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash, python, typescript and go).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Coordination Discipline loads about 3.8k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 1,018 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 1,018 words, ~3,813 tokens.

Download SKILL.mdSave it as .claude/skills/agent-coordination-discipline/SKILL.md (or your agent's skills folder).
name
agent-coordination-discipline
description
Use when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents. Covers delegation criteria, external-model patterns, task isolation, and agent selection strategies.
keywords
agent-coordination, external-model, task-isolation, delegation-criteria, multi-agent, external-model, claudish, orchestration, agent-selection, Task-tool…
created
2026-01-20
updated
2026-01-20
plugin
dev
type
discipline
difficulty
intermediate

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
2. Task Isolation Requirements

Every agent task must be independently executable:

Bad (not isolated):

Task: "Fix the bug we discussed earlier"

Good (properly isolated):

Task: "Debug the TypeError in src/components/UserProfile.tsx line 42.
Context: User reports 'Cannot read property name of undefined' when viewing profile page.
Evidence: Error occurs after recent commit abc123 that changed user data structure.
Success criteria: Identify root cause, propose fix, verify with test scenario."
3. External Model Pattern

When delegating to external models via claudish CLI:

Structure:

bash
claudish --model {model_id} --stdin --quiet <<EOF > output.md
{Task Description}

Context:
- {Relevant file paths}
- {Current state}
- {Related decisions}

Success Criteria:
- {What constitutes success}
- {Expected output format}

Constraints:
- {Time limits}
- {Tool restrictions}
- {Quality requirements}
EOF

Example:

bash
claudish --model x-ai/grok-code-fast-1 --stdin --quiet <<EOF > analysis.md
Analyze the React component rendering performance issue in Dashboard.tsx.

Context:
- File: src/components/Dashboard.tsx (247 lines)
- Issue: Component re-renders 40+ times on data updates
- Recent changes: Added real-time WebSocket updates in commit f4a2c1b

Success Criteria:
- Identify unnecessary re-renders (provide line numbers)
- Propose memoization strategy
- Estimate performance improvement

Constraints:
- Max 3 minutes analysis time
- Focus on React 19 compiler-friendly patterns
EOF

When to Use Agents

Multi-Step Investigation

Trigger: Task requires 5+ tool calls with conditional branching Agent: developer, architect Example: "Trace data flow through 3 layers to find where user.email becomes null"

External Model Expertise

Trigger: Need specialized model capabilities (code speed, vision, reasoning) Agent: external-model with specific model Example: "Use Grok Code Fast to refactor 15 files for consistency in < 2 minutes"

Parallel Work

Trigger: Multiple independent tasks that can run simultaneously Agent: Multiple Task calls with result aggregation Example: "Analyze frontend performance (Task 1) while auditing API security (Task 2)"

Risk Isolation

Trigger: High-risk changes needing review before merging to main workflow Agent: review-focused agent with checkpoint Example: "Evaluate if this database migration will cause downtime"

Skill Gaps

Trigger: Current agent lacks specific skill that another agent has Agent: specialist agent (security, performance, accessibility) Example: "Launch accessibility agent to audit ARIA compliance"

When NOT to Use Agents

Single Grep/Glob

Instead: Use native Grep or Glob tool directly

# ✗ DON'T
Task: "Find all files using the deprecated API"

# ✓ DO
Grep("oldApiCall", output_mode: "files_with_matches", type: "js")
Simple Tool Execution

Instead: Use tool directly

# ✗ DON'T
Task: "Read the config file and tell me the API URL"

# ✓ DO
Read("/path/to/config.json")
// Parse and extract apiUrl field
Decision Already Made

Instead: Execute the decision

# ✗ DON'T
Task: "I think we should use React Query. What do you think?"

# ✓ DO
// Just implement React Query since decision is made
Write("src/hooks/useApiQuery.ts", reactQueryCode)
Sequential Tool Calls

Instead: Chain tools directly

# ✗ DON'T
Task: "Find the function, read it, and edit it"

# ✓ DO
Grep("functionName", output_mode: "files_with_matches")
// => result: src/utils/helper.ts
Read("src/utils/helper.ts")
Edit("src/utils/helper.ts", old_string, new_string)
Nuanced Context Required

Instead: Handle in current agent

# ✗ DON'T
Task: "Based on our earlier discussion about performance vs. maintainability trade-offs, decide if we should cache this"

# ✓ DO
// Current agent already has context, make decision directly
if (performanceIsCritical) {
  implementCaching()
}

Agent Selection Matrix

Task TypeBest AgentModelReasoning
Debugging errorsdevelopersonnet-4-5Deep reasoning, context retention
Design reviewarchitectsonnet-4-5System thinking, trade-off evaluation
Code generationdevelopergrok-code-fastSpeed for repetitive patterns
Multi-codebase analysisdevelopersonnet-4-5Cross-repo understanding
Performance profilingdeveloper + external-modelgrok-code-fastFast scanning + specific optimization
Security auditsecurity (if available)sonnet-4-5Nuanced threat modeling
Documentation generationdevelopergrok-code-fastFast, straightforward task
Refactoring (large scope)developersonnet-4-5Maintain consistency across changes

external-model Pattern Details

1. Model Selection

Fast Execution (< 2 min):

  • x-ai/grok-code-fast-1 - Code generation, refactoring, simple analysis
  • anthropic/claude-3-5-haiku - Quick decisions, data transformation

Deep Reasoning (> 2 min):

  • anthropic/claude-sonnet-4-5 - Complex debugging, architecture design
  • google/gemini-2.0-flash-thinking-exp-01-21 - Extended thinking budget

Specialized:

  • Vision models - Screenshot analysis, diagram interpretation
  • Code models - Language-specific optimization
2. Context Packaging

Minimal (< 1000 tokens):

  • File paths only
  • Error message
  • Success criteria

Moderate (1000-5000 tokens):

  • Key code snippets (< 50 lines)
  • Related file structure
  • Recent commit context

Full (5000+ tokens):

  • Complete file contents
  • Related test files
  • Architecture documentation
Show full SKILL.md (410 more words)Show less
3. Success Criteria Definition

Must include:

  • Output format - JSON, markdown, code snippet, report
  • Completeness - What must be covered
  • Quality bar - Minimum acceptable quality
  • Constraints - Time, token, tool limits

Example:

Success Criteria:
- Output: JSON array of {file, line, issue, suggestion}
- Completeness: All React components in src/ analyzed
- Quality: Each suggestion must include before/after code
- Constraints: Complete within 5 minutes, use only Read/Grep tools
4. Result Routing

Pattern:

1. Launch agent with external-model
2. Capture result in variable or file
3. Validate result against success criteria
4. Route to next step:
   - If success: Use result in main workflow
   - If partial: Request clarification
   - If failure: Fall back to native tools

Example:

result = Task("external-model: x-ai/grok-code-fast-1\n\nRefactor 10 components for React 19...")

if (result.contains("Refactored successfully")) {
  // Apply changes to codebase
  applyRefactorings(result.changes)
} else {
  // Fall back to manual refactoring
  manualRefactor()
}

Task Isolation Checklist

Before launching an agent, verify:

  • Independent understanding - Task description is self-contained (no "as discussed", "the bug we saw")
  • Success criteria defined - Clear definition of what "done" looks like
  • Dependencies listed - All required files, services, credentials specified
  • Result format specified - Expected output structure (JSON, markdown, code, report)
  • Error handling clear - What happens if agent fails or returns partial results
  • Timeout reasonable - Time limit matches task complexity
  • Tool attempts exhausted - Tried native tools first, agent is not premature
  • Model selection justified - Chosen model matches task requirements (speed vs. reasoning)

Examples

Example 1: Bad Agent Usage (Python)
python
# ✗ VIOLATION: Agent for single grep
Task: "Find all files importing the old database client"

# ✓ CORRECT: Use native tool
Grep("from old_db_client import", type: "py", output_mode: "files_with_matches")
Example 2: Good Agent Usage (TypeScript)
typescript
// ✓ CORRECT: Multi-step investigation with agent
Task: "Debug the race condition in WebSocket message handling.

Context:
- File: src/services/websocket.ts (342 lines)
- Issue: Messages arrive out of order 5% of the time
- Environment: Production only (not reproducible in dev)
- Recent changes: Added message batching in commit a3f9c21

Success Criteria:
- Identify race condition root cause (provide line numbers)
- Propose synchronization strategy
- Verify solution handles edge cases

Constraints:
- Max 10 minutes analysis
- Use Read, Grep, and Bash tools only
- No code changes (diagnosis only)"
Example 3: external-model with External Model (Go)
go
// ✓ CORRECT: Fast refactoring with Grok
external-model: x-ai/grok-code-fast-1

Refactor 15 handler functions in handlers/ to use consistent error handling pattern.

Context:
- Directory: internal/handlers/ (15 files, ~200 lines each)
- Current state: Inconsistent error responses (some use Error(), some use Errorf(), some return raw errors)
- Target pattern: Use custom AppError type with status codes and messages

Success Criteria:
- All 15 handlers use AppError consistently
- Preserve existing business logic (only change error handling)
- Provide git diff summary

Constraints:
- Complete within 3 minutes
- Use Read and Grep tools for analysis
- Return refactored code for all 15 files

Integration with Other Skills

Works with:

  • verification-before-completion - Validate agent results before marking tasks complete
  • systematic-debugging - Use agents for multi-step debugging investigations
  • orchestration skills - Multi-agent coordination patterns from orchestration plugin

Prevents:

  • Premature agent launches - Check delegation criteria first
  • Agent thrashing - Avoid launching agents that just launch more agents
  • Budget waste - Don't use slow models for fast tasks or vice versa

Anti-Patterns Table

Anti-Pattern✗ Without Discipline✓ With Discipline
Trivial task delegationLaunch agent to run single grepUse Grep tool directly
Missing isolation"Fix the bug we discussed""Debug TypeError in UserProfile.tsx line 42: 'Cannot read property name of undefined'. Context: ..."
No success criteria"Analyze the performance issue""Identify re-render causes (line numbers), propose memoization, estimate improvement %"
Wrong model selectionUse sonnet-4-5 for simple refactoringUse grok-code-fast for speed
No result validationLaunch agent, assume successCheck result against success criteria, have fallback plan
Coordination failureLaunch 3 agents, hope they coordinateDefine result routing: Agent 1 → validate → Agent 2 → aggregate

Enforcement Mechanism

Detection:

  1. Before Task tool call, check if task description includes success criteria
  2. Before external-model, verify model name is explicitly specified
  3. Before agent launch, confirm native tools were attempted first
  4. After agent completes, verify result is validated before use

Correction:

  1. If missing success criteria → Add "Success Criteria:" section to task description
  2. If trivial task → Cancel agent launch, use native tool
  3. If wrong model → Reconsider model selection based on task requirements
  4. If result unused → Add validation and routing logic

Validation:

Agent Task Checklist (all must be true):
✓ Task requires 5+ tool calls OR external model expertise
✓ Success criteria defined (output format, completeness, quality bar)
✓ Context is self-contained (no references to earlier discussion)
✓ Model selection justified (speed vs. reasoning trade-off considered)
✓ Result routing planned (validation + next steps)
✓ Error handling defined (fallback if agent fails)
✓ Native tools attempted first (or explicitly not applicable)

Related Skills:

  • verification-before-completion - Validate agent results
  • systematic-debugging - Multi-step debugging investigations
  • orchestration/multi-agent-orchestration - Complex coordination patterns

Version: 1.0.0 Last Updated: 2026-01-20

© MadAppGang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/dev/skills/discipline/agent-coordination-discipline of MadAppGang/claude-code.

Open the folder on GitHubat commit 6097ad4

Compare with similar skills

Agent Coordination Discipline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Coordination Discipline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Coordination Discipline this skillMadAppGang/claude-code285—~3.8kAutomated safety check: PassMIT
Orca CLIstablyai/orca89k2 repos~593Automated safety check: PassMIT
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Mission Control Agent APIbuilderz-labs/mission-control6.3k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    89k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed
  • Mission Control Agent API

    builderz-labs/mission-control

    Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.

    6.3k GitHub stars~2.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

More from MadAppGang/claude-code

All 69 skills in this repo
  • Content Brief

    MadAppGang/claude-code

    Content brief template and creation methodology for SEO-optimized content.

    285 GitHub starsUsed in 1 repo~959 tokens
    Auto-check passed
  • Context Detection

    MadAppGang/claude-code

    A skill your agent uses when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g…

    285 GitHub stars~5.4k tokensUpdated 7 mo ago
    Auto-check passed
  • Content Optimizer

    MadAppGang/claude-code

    On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.

    285 GitHub starsUsed in 1 repo~694 tokens
    Auto-check passed
  • Keyword Cluster Builder

    MadAppGang/claude-code

    Techniques for expanding seed keywords and clustering by topic and intent.

    285 GitHub starsUsed in 1 repo~674 tokens
    Auto-check passed
  • Serp Analysis

    MadAppGang/claude-code

    SERP analysis techniques for intent classification, feature identification, and competitive intelligence.

    285 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Agent Enforcement

    MadAppGang/claude-code

    Multi-agent orchestration enforcement for /team command. An agent skill from MadAppGang/claude-code.

    285 GitHub stars~895 tokensUpdated 7 mo ago
    Auto-check passed

Categories

Questions about Agent Coordination Discipline

What does Agent Coordination Discipline do?

A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents. Agent Coordination Discipline is an agent skill from MadAppGang/claude-code. Use when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

When should I use Agent Coordination Discipline?

Agent Coordination Discipline fits situations like: deciding whether to launch an agent; selecting which agent to use; coordinating multiple agents.

How do I install Agent Coordination Discipline in Claude Code?

Run `npx skills add MadAppGang/claude-code --skill agent-coordination-discipline -a claude-code`. Or copy the skill folder (plugins/dev/skills/discipline/agent-coordination-discipline in MadAppGang/claude-code) into .claude/skills/agent-coordination-discipline in your project. Claude Code loads it when a task matches its description.

How do I install Agent Coordination Discipline in Codex?

Run `npx skills add MadAppGang/claude-code --skill agent-coordination-discipline -a codex`. Or copy the skill folder (plugins/dev/skills/discipline/agent-coordination-discipline in MadAppGang/claude-code) into .agents/skills/agent-coordination-discipline in your project. Codex loads it when a task matches its description.

Can I use Agent Coordination Discipline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MadAppGang/claude-code --skill agent-coordination-discipline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-coordination-discipline, .gemini/skills/agent-coordination-discipline, .github/skills/agent-coordination-discipline and .opencode/skills/agent-coordination-discipline in your project.

What does Agent Coordination Discipline need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Coordination Discipline is instructions for the agent only. Our summary lists: Python 3.

Does Agent Coordination Discipline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Coordination Discipline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Coordination Discipline use?

Agent Coordination Discipline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Coordination Discipline use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Coordination Discipline?

Skills that share tags, products or a category with Agent Coordination Discipline: Orca CLI (stablyai/orca, 89k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Coordination Discipline?

MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.

Source: MadAppGang/claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.