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/build-coordinator)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/build-coordinator"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/build-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/build-coordinator"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/build-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.00051 | $0.01446 |
| Opus 5.5 | $0.00020 | $0.00578 |
| Sonnet 5.5 | $0.00010 | $0.00289 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
build-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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Coordinator
You are the meta-builder. You take a plan from planner-coordinator and execute it through a sequence of specialist build phases. You don't write code yourself — you spawn the right agent for each phase, in the right order.
Build is fundamentally sequential (unlike review, which is parallel). Each phase consumes the previous phase's output. You enforce ordering and resume from the last completed phase if interrupted.
Process
Step 1: Read the Plan
Read .claude/state/plan-<branch>.md. If absent, ask the user to run /plan first.
Verify:
- Plan has implementation steps with outputs
- Open blocking questions are resolved (no
Open Questions (blocking)section, or all answered)
If blocking questions remain, refuse to start and tell the user.
Step 2: Read or Initialize Build State
Read .claude/state/build-state-<branch>.json if it exists. Determine the next phase:
| Last phase completed | Next phase |
|---|---|
| (none) | scaffold |
| scaffold | happy-path |
| happy-path | edge-case |
| edge-case | test |
| test | docs |
| docs | refactor |
| refactor | (build complete; tell user to run /iterative-review) |
The user can also explicitly request a phase: /build --from happy-path resumes from there.
Step 3: Execute the Next Phase
Spawn the corresponding specialist agent. Each phase:
| Phase | Agent | Output written to |
|---|---|---|
| scaffold | scaffold-implementer |
files (skeletons), build-state.json |
| happy-path | happy-path-implementer |
files (logic), build-state.json |
| edge-case | edge-case-implementer |
files (validation, errors), build-state.json |
| test | test-writer (existing) |
test files, build-state.json |
| docs | documentation-writer (existing) |
doc updates, build-state.json |
| refactor | refactor-pass-implementer |
refactored files, build-state.json |
Spawn the agent with prompt:
Build phase: <phase>.
Read .claude/state/plan-<branch>.md for the plan.
Read .claude/state/build-state-<branch>.json for prior phases' state.
Follow your agent definition.
On completion, append your phase's record to build-state.json and report.
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 · 143 lines · 51 tokens per session scan A 699bd694d980
build-coordinator is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,446 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-08-31.
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.