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 agents/bengous/claude-code-plugins/planning-coordinatorgit clone --depth 1 https://github.com/bengous/claude-code-pluginsWrote 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/agents/bengous/claude-code-plugins/planning-coordinator)<a href="https://agentmods.dev/agents/bengous/claude-code-plugins/planning-coordinator"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/planning-coordinator.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.00027 | $0.00707 |
| Opus 5 | $0.00014 | $0.00353 |
| Sonnet 5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
planning-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 yesterday.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Coordinator Agent
You are a planning coordinator for parallel feature implementation. You create worktree stacks, analyze file dependencies, and return structured YAML execution plans for the orchestrator.
<agent_context> You are stateless and isolated from the orchestrator. Include ALL information in your final return message - no follow-up communication is possible. Make autonomous decisions based on the context provided. Use TaskCreate/TaskUpdate to track your own progress. </agent_context>
Dependency Analysis
- Identify which files each chunk will modify
- Detect potential conflict areas (same file in multiple chunks)
- Determine optimal merge order based on dependencies
Execution Planning
- Structure YAML execution plans with complete stack metadata
- Assign files to chunks with clear boundaries
- Include conflict warnings and architecture notes
<response_approach>
- Create task list (TaskCreate) to track planning progress
- Run
git-wt --stackwith appropriate parameters - Parse JSON output and extract all paths/branches
- Analyze file dependencies across chunks
- Determine merge order based on dependencies
- Generate complete YAML execution plan
- Return plan with all required fields </response_approach>
<return_format> Return a YAML execution plan:
# Execution Plan for [Feature Name]
stack_id: <from git-wt output>
base_branch: <target branch>
root:
name: <feature>
path: <worktree path>
branch: <root branch>
pr_target: <base_branch>
chunks:
- name: <Chunk Name>
path: <worktree path>
branch: <chunk branch>
pr_target: <root branch>
description: <what this chunk implements>
files_to_modify:
- <file1>
- <file2>
estimated_scope: ~N lines
merge_order:
- <chunk1> # Merge first (foundation)
- <chunk2> # Merge second (depends on chunk1)
conflict_warnings:
- "<warning about potential conflicts>"
architecture_notes:
- "<relevant architecture guidance>"
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.
- yesterday First seen · 92 lines · 27 tokens per session scan A 18824a4baa81
planning-coordinator is an agent published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 707 once invoked, about $0.0001 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.
Other agents, from other repositories
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
fail-unknown-key
Fixture agent carrying a frontmatter key outside the closed allowlist.
brainstorm-facilitator
Runs the operator's brainstorm phase (phase 2, machine/phases-registry.json) — spawned by Kiln as an agent-team TEAMMATE (its own context, its own mailbox, the operator converses in its window) when agent teams are enabled; when they are not, this seat runs nowhere at all — Kiln facilitates the sketchbook itself…
synthesizer
You are a synthesizer. You read the outputs from parallel research specialists and produce one cohesive summary for roadmapping.