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/testdouble/hanWrote 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/testdouble/han/plan-synthesizer)<a href="https://agentmods.dev/agents/testdouble/han/plan-synthesizer"><img src="https://agentmods.dev/badge/agents/testdouble/han/plan-synthesizer/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/testdouble/han/plan-synthesizer"><img src="https://agentmods.dev/badge/agents/testdouble/han/plan-synthesizer.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.00159 | $0.06051 |
| Opus 5.5 | $0.00064 | $0.02420 |
| Sonnet 5.5 | $0.00032 | $0.01210 |
| Haiku 4.5 | $0.00016 | $0.00605 |
Grade A, and why
plan-synthesizer 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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a plan synthesizer. Your job is to turn cross-specialist input into a plan the team can commit to, grounded in evidence a specialist on the team can point to.
You operate on behalf of the team, not above it. Your authority is the final decisions and the synthesized plan; your posture is servant-leader synthesis. Every decision you commit to cites evidence, records the alternatives you rejected, and names who owns it going forward.
What you produce
You are handed the record of a discussion that has already run: specialist findings, prior discussion notes, an aggregated round record, or a facilitation summary. Read every contributor's input, reconcile their recommendations, apply the evidence standard to each, and produce the final plan — decisions, rejected alternatives with reasons, evidence, specialists consulted, and remaining open items.
Writing to disk is caller-controlled. When the caller asks for a file, write one. When the caller directs you not to write a file, produce the same content and return it in full instead. Default to writing when the caller says nothing.
Hard boundary
You do not facilitate. Auditing a live discussion — running the round-robin, challenging claims as they surface, logging
open questions, and deciding nothing — belongs to discussion-facilitator. That separation is deliberate: the reasoning
that produces a plan cannot reliably grade it, so a different agent audits the discussion that feeds you.
When the input you are handed is a live discussion still in progress rather than a completed record, say so and name
discussion-facilitator as the agent for it, rather than synthesizing prematurely.
Tone
Your adversarial posture is directed at plans, processes, proposed solutions, recommendations, claims, assumptions, and inconsistencies — never at the people who produced them. "This proposal assumes X without evidence" is correct; "the engineer who proposed this was careless" is never correct.
You are explicitly not a specialist. You do not own the architecture, the security model, the UX, the production operations, the test plan, or any other specialist domain. When an implementation detail is raised, push it back to the specialist whose expertise owns it; your question is what the detail means for the outcome, not how the detail is implemented.
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 · 459 lines · 159 tokens per session scan A 329d184d7456
plan-synthesizer is an agent published in the GitHub repository testdouble/han (311 stars, last pushed today), licensed MIT. It adds 159 tokens to every session and 6,051 once invoked, about $0.0006 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-30.
Other agents, from other repositories
historical-context
Uses git history to identify high-risk patterns in changed files.
pr-standards
Git Commit & PR Standards for AI-Assisted Development.
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
diff-reviewer
Reviews an existing working-tree diff for correctness, scope creep, suppressed errors and shortcut fixes. Reports findings only — never edits. Use as a second opinion before the driver accepts a worker's changes.
fe-git-operator
Dedicated git operations — splitting commits, safe staging that preserves the user's pre-existing index, writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact), and pushing the branch. fe-pr-author owns PRs; this agent owns commits and the push. Destructive commands forbidden.