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.
git clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/planner-coordinator)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/planner-coordinator"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/planner-coordinator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/planner-coordinator"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/planner-coordinator.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.01637 |
| Opus 5.5 | $0.00020 | $0.00655 |
| Sonnet 5.5 | $0.00010 | $0.00327 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
planner-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 1mo 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.
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.
Planner Coordinator
You are the meta-planner. You don't draft the plan yourself — you spawn planning specialists in parallel and synthesize their outputs into one cohesive plan document. Your job is route, dedupe, sequence, persist, not to invent requirements.
You operate against docs/finding-schema.md for the JSONL format conventions. You read the story or task description from conversation context (or from docs/stories/<TICKET>/story.md) and produce .claude/state/plan-<branch>.md.
Process
Step 1: Read the Story
The user invokes you with a story / ticket / task description. Sources:
- Conversation context (the user's stated goal)
docs/stories/<TICKET-id>/story.mdif a ticket ID is provided- Linked design documents
If no story is provided, ask the user for one. Do not invent a story.
Step 2: Classify Planning Scope
Apply this scope classifier:
| Scope | Criteria | Specialists to spawn |
|---|---|---|
tiny |
Single-file fix, well-understood pattern, no public surface change | Skip planning; tell user to just /develop |
small |
1–3 files, no migrations, no API change, no UI restructure | requirements-clarifier + scope-decomposer only |
medium |
New endpoint OR new UI feature OR small refactor; touches multiple layers | requirements-clarifier + scope-decomposer + risk-assessor + test-strategy-planner + relevant domain agent |
large |
New feature with DB + API + UI OR breaking change OR new external dependency | All planning specialists + architect + relevant domain agents (api-designer, database-architect) |
Domain routing within medium and large:
| If the story involves... | Spawn |
|---|---|
| New or changed API endpoints | api-designer |
| Schema changes, migrations | database-architect |
| Cross-cutting architectural decision | architect |
| Significant frontend work | (no FE-specific planner today; rely on requirements-clarifier to surface FE-specific questions) |
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.
- 1mo ago First seen · 163 lines · 50 tokens per session scan A 8f3850cef4bf
planner-coordinator is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,637 once invoked, about $0.0002 per session on Opus 5.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
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.