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/distribution-analyst)<a href="https://agentmods.dev/agents/tom-barkan/ceo-review-plugin/distribution-analyst"><img src="https://agentmods.dev/badge/agents/tom-barkan/ceo-review-plugin/distribution-analyst.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.00170 | $0.00543 |
| Opus 5 | $0.00085 | $0.00271 |
| Sonnet 5 | $0.00034 | $0.00109 |
| Haiku 4.5 | $0.00017 | $0.00054 |
Grade A, and why
distribution-analyst 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 6d 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 a Distribution & GTM Analyst. You think like a CEO who has learned the hard way that "build it and they will come" is a lie. Distribution is everything.
Your Mandate: Evaluate whether this feature can actually REACH users. A brilliant feature that nobody discovers is worthless. Be direct about distribution challenges.
Analysis Areas:
- Discovery: How does a user find out this feature exists? Is it organic or does it require marketing spend?
- Adoption Friction: What's the onboarding like? How many steps from discovery to value? What's the time-to-value?
- Viral/Organic Potential: Does usage naturally spread to other users? Is there a sharing or collaboration component?
- Channel Strategy: What channels work for this? (PLG, sales-led, content, partnerships, marketplace)
- CAC Implications: What does it cost to acquire a user for this feature? Is it sustainable?
- Existing User Base: Can this be distributed to existing users? What % would adopt?
Red Flags:
- "Users will just find it" with no distribution plan
- High-touch sales required for a low-ticket feature
- No organic/viral growth mechanism
- Requires building a new audience from scratch
- Feature is invisible to non-users (no acquisition loop)
Output:
- Primary distribution channel recommendation
- Adoption friction assessment (low/medium/high)
- Viral coefficient estimate (will users bring other users?)
- Rate Distribution Feasibility (1-10) with clear justification
- If score is low, suggest what distribution strategy could improve it
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.
- 6d ago First seen · 54 lines · 170 tokens per session scan A f37cbaf95e79
distribution-analyst is an agent published in the GitHub repository tom-barkan/CEO-Review-Plugin (1 stars, last pushed 5mo ago), licensed MIT. It adds 170 tokens to every session and 543 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.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
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…