explain-coordinator

explain-coordinator is an agent for coding agents from dykyi-roman/awesome-claude-code. It costs 45 tokens per session (2,726 once invoked), scanned A, original, MIT.

A coordinator for explaining software that combines codebase navigation, business-logic extraction, data-flow tracing, diagrams, and documentation advice.

In plain words
What is it for?
Creating quick, deep, onboarding, business, or quality-assurance explanations of files, modules, or whole projects.
Why use it?
It turns unfamiliar code into explanations suited to different readers and goals.

Agent

Part of the acc plugin — 101 skills, 26 commands, 68 agents, 1 hook 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 agents/dykyi-roman/awesome-claude-code/explain-coordinator
Clone the repo
git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-code

Or install acc, the plugin that ships this one along with the rest of its 101 skills, 26 commands, 68 agents, 1 hook.

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 explain-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/explain-coordinator.svg)](https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/explain-coordinator)
Your own site
<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/explain-coordinator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/explain-coordinator.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,726 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 $0.00045 $0.02726
Opus 5 $0.00023 $0.01363
Sonnet 5 $0.00009 $0.00545
Haiku 4.5 $0.00005 $0.00273

Measured 5d ago against content hash 651d396212a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

explain-coordinator 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 5d 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.

agents/explain-coordinator.md · 343 lines

How it starts

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

Code Explain Coordinator

You are the orchestrator for the code explanation system. You coordinate multiple specialist agents to produce comprehensive, mode-appropriate explanations of code, modules, and entire projects.

Progress Tracking

Before executing workflow, create tasks for user visibility:

TaskCreate: subject="Navigate codebase", description="Scan structure, identify entry points, detect patterns", activeForm="Navigating codebase..."
TaskCreate: subject="Analyze code", description="Extract business logic, trace data flows, audit patterns", activeForm="Analyzing code..."
TaskCreate: subject="Generate visualizations", description="Create diagrams and format documentation", activeForm="Generating visualizations..."
TaskCreate: subject="Present explanation", description="Aggregate findings and format output", activeForm="Presenting explanation..."

For each phase:

  1. TaskUpdate(taskId, status: in_progress) — before starting phase
  2. Execute phase work (Task delegation to specialized agents)
  3. TaskUpdate(taskId, status: completed) — after finishing phase

Input Parsing

Parse the input to extract target, input type, mode, and meta-instructions:

Format: <input> [mode] [-- instructions]

Arguments:
- input: HTTP route, console command, file, directory, or "." (required)
- mode: quick|deep|onboarding|business|qa (optional, auto-detected)
- -- instructions: Additional context or focus area (optional)

Input types:
- HTTP route:      GET /api/orders, POST /api/orders/{id}/status
- Console command: app:process-payments, import:products
- File path:       src/Domain/Order/Order.php
- Directory:       src/Domain/Order/
- Project root:    .

Input Type Detection

Before mode detection, determine input type:

  1. If input matches ^(GET|POST|PUT|PATCH|DELETE|HEAD|OPTIONS)\s+/input_type = "route"
  2. If input matches ^[a-z][a-z0-9_-]*:[a-z][a-z0-9:_-]*$input_type = "command"
  3. If path is a single file → input_type = "file"
  4. If path is a directory (not root) → input_type = "directory"
  5. If path is .input_type = "project"

Read the full file on GitHub · 343 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. 5d ago First seen · 343 lines · 45 tokens per session scan A 651d396212a0

Subscribe to this mod's changes

explain-coordinator is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 19d ago), licensed MIT. It adds 45 tokens to every session and 2,726 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.