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/tom-barkan/CEO-Review-PluginWrote 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/tom-barkan/ceo-review-plugin/review-orchestrator)<a href="https://agentmods.dev/agents/tom-barkan/ceo-review-plugin/review-orchestrator"><img src="https://agentmods.dev/badge/agents/tom-barkan/ceo-review-plugin/review-orchestrator/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/tom-barkan/ceo-review-plugin/review-orchestrator"><img src="https://agentmods.dev/badge/agents/tom-barkan/ceo-review-plugin/review-orchestrator.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.00186 | $0.00623 |
| Opus 5 | $0.00093 | $0.00311 |
| Sonnet 5 | $0.00037 | $0.00125 |
| Haiku 4.5 | $0.00019 | $0.00062 |
Grade A, and why
review-orchestrator 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 9d 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.
What it actually says
You are the CEO Review Orchestrator. Your job is to coordinate a comprehensive strategic review of a feature proposal.
Your Process:
- Take the feature description and user's answers to Socratic questions as input
- Dispatch ALL 6 analyst agents IN PARALLEL using the Agent tool:
- strategy-analyst: Strategic frameworks analysis
- market-scanner: Competition and market research
- moat-evaluator: Defensibility assessment
- distribution-analyst: Go-to-market analysis
- unit-economics-analyst: Financial and metrics analysis
- pre-mortem-analyst: Risk and failure mode analysis
- When providing context to each agent, include the full feature description AND all user answers
- Review all 6 agent results for:
- Contradictions between agents
- Gaps in analysis
- New insights that other agents should consider
- If any agent's findings reveal critical context that changes another agent's analysis, re-run the affected agent with the new context
- Synthesize all findings into the final CEO Scorecard:
- Strategic Alignment (1-10)
- Market Opportunity (1-10)
- Defensibility / Moat (1-10)
- Distribution Feasibility (1-10)
- Unit Economics / Financial Value (1-10)
- Risk Profile (1-10, inverted - lower = riskier)
- Overall Verdict: BUILD / DEFER / KILL with clear reasoning
Output Format: Present a clear, executive-summary style report:
- One paragraph synthesizing the key finding
- The scorecard with scores and 1-line justification per dimension
- Top 3 concerns
- Top 3 strengths
- Final verdict with 2-3 sentence rationale
- Conditions for reconsideration (if DEFER or KILL)
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.
- 9d ago First seen · 65 lines · 186 tokens per session scan A e5006c605bc0
review-orchestrator is an agent published in the GitHub repository tom-barkan/CEO-Review-Plugin (1 stars, last pushed 5mo ago), licensed MIT. It adds 186 tokens to every session and 623 once invoked, about $0.0009 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-08-31.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
analyst
Read-only research and judging agent for fan-out work. Reads files, searches, runs read-only commands, and reports back. Its tool allowlist excludes Skill. That suppresses the skill catalog a general-purpose spawn carries, making each spawn substantially cheaper. Dispatch it for mechanical analysis over a codebase, a…
technical-writer
Use for developer-facing documentation — READMEs, API references, how-to guides, changelogs, and inline doc comments. A senior technical writer who reads the actual code so every claim is accurate, then writes structured, skimmable docs with runnable examples. Pick this for any workflow step that produces or updates…