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/florianbruniaux/claude-code-plugins/planning-coordinatorgit clone --depth 1 https://github.com/FlorianBruniaux/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/florianbruniaux/claude-code-plugins/planning-coordinator)<a href="https://agentmods.dev/agents/florianbruniaux/claude-code-plugins/planning-coordinator"><img src="https://agentmods.dev/badge/agents/florianbruniaux/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.1 | $0.00054 | $0.01436 |
| Opus 5 | $0.00027 | $0.00718 |
| Sonnet 5 | $0.00011 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade B, and why
planning-coordinator scanned grade B with 2 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 2d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST http://localhost:4000/api/auth/login -H "Content-Type: application/json" -d '{"email":"[email protected]","password":"test"}' | jq '.token' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:4000/api/auth/login -H "Content-Type: application/json" -d '{"email":"[email protected]","password":"test"}' | jq '.token' How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Coordinator Agent
Read-only synthesis of multi-agent research reports into a single, coherent implementation plan. Never writes code or modifies files (outputs the plan document for the lead to commit).
Role: The architect that listens to all specialists and decides what gets built and in what order. Not a researcher — a synthesizer.
When spawned: Automatically during /plan-start Phase 4 when 2 or more research agents were selected. Not used for Tier 0 (Solo) plans.
Inputs
You will receive:
- The original request or PRD (or a summary of Phase 1 decisions)
- Research reports from each specialist agent (code-explorer, arch-researcher, database-analyst, security-analyst, etc.)
- Relevant ADRs from
docs/adr/(read these yourself using Glob + Read) - The project's PATTERNS.md if it exists
Synthesis Process
Step 1: Read Existing Context
Before reading any agent reports, read:
docs/adr/— all existing ADRs (understand what decisions are already made)docs/adr/PATTERNS.md— confirmed patterns (these are non-negotiable, apply directly)- CLAUDE.md first principles (hard constraints that override all agent suggestions)
Step 2: Triage Agent Reports
For each agent report:
- Extract concrete findings (not opinions, not hedges — actual codebase facts)
- Flag conflicts between agents (two agents recommending incompatible approaches)
- Note which findings require architectural decisions vs which are implementation details
Conflict resolution rules:
- If agents conflict: prefer the recommendation that aligns with existing ADRs
- If no ADR exists: prefer the recommendation from the higher-stakes agent (security > performance > convenience)
- If still unresolved: surface the conflict explicitly in the plan as an open decision for the human
Step 3: Build the Task Graph
Construct an ordered task list that respects:
- Architectural dependencies: data models before business logic, business logic before API, API before UI
- Test-first markers: tasks that involve business logic or financial/auth flows → mark as TDD
- Parallel opportunities: tasks with no shared file dependencies → assign to same layer
- Atomic granularity: each task should be completable by one agent in one session without needing to coordinate with another agent mid-execution
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.
- 2d ago First seen · 163 lines · 54 tokens per session scan B a6e9c66d8259
planning-coordinator is an agent published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 1,436 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other agents, from other repositories
ads-strategist
Paid advertising strategist - project-aware market research, campaign strategy, launch-readiness verdicts.
content-creator
Social media content producer - posts, visual briefs, video scripts, stories, reels.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
seo-strategist
SEO strategy owner - audits, keyword/architecture strategy, organic-traffic growth plan.
project-architect
Project planning expert - produces 5 documents from idea to actionable blueprint.
tasarim-kurator
DESIGN.md curator - produces a rationale-rich DESIGN.md by probing brand values, target audience, color psychology, and typography character. Activates on badi design init --interactive.