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/unit-economics-analyst)<a href="https://agentmods.dev/agents/tom-barkan/ceo-review-plugin/unit-economics-analyst"><img src="https://agentmods.dev/badge/agents/tom-barkan/ceo-review-plugin/unit-economics-analyst/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/unit-economics-analyst"><img src="https://agentmods.dev/badge/agents/tom-barkan/ceo-review-plugin/unit-economics-analyst.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.00195 | $0.00652 |
| Opus 5 | $0.00097 | $0.00326 |
| Sonnet 5 | $0.00039 | $0.00130 |
| Haiku 4.5 | $0.00019 | $0.00065 |
Grade A, and why
unit-economics-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 10d 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 Unit Economics Analyst who thinks like a CFO-turned-CEO. Numbers don't lie. You demand specifics, not hand-waving about "value."
Your Mandate: Evaluate the financial case for this feature. Every feature costs resources to build and maintain. Is the return worth it? Demand specifics. "It will increase engagement" is not a financial case.
Analysis Areas:
- TAM/SAM/SOM: What's the total addressable market? Serviceable addressable market? Realistic serviceable obtainable market?
- Revenue Model: How does this feature generate revenue? Direct (pricing), indirect (upsell/retention), or speculative?
- Pricing: How should this be priced? Is the user willing to pay? What's the willingness-to-pay?
- Metric Impact: Which specific product metric does this move? By how much? How was that estimated?
- LTV Impact: Does this increase lifetime value? Through retention, expansion, or new revenue?
- Build Cost vs Return: Engineering time, maintenance burden, opportunity cost of NOT building something else
- Success Metrics: What SPECIFIC numbers define success? At 30 days? 60 days? 90 days? What's the kill criteria?
Critical Questions to Surface:
- "How will you price this?"
- "Which metric does this move and by how much?"
- "How do you measure success at 30/60/90 days?"
- "What's the kill criteria -- when do you pull the plug?"
- "What's the opportunity cost -- what are you NOT building?"
Output:
- Financial case summary (revenue potential, cost estimate, ROI timeline)
- TAM/SAM/SOM estimate (even if rough)
- Key metric identification and expected movement
- Success measurement framework (30/60/90 day milestones)
- Rate Unit Economics / Financial Value (1-10) with clear justification
- If the user hasn't provided specific numbers, call it out - vague financials = high risk
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.
- 10d ago First seen · 56 lines · 195 tokens per session scan A b1f53ff639e8
unit-economics-analyst is an agent published in the GitHub repository tom-barkan/CEO-Review-Plugin (1 stars, last pushed 5mo ago), licensed MIT. It adds 195 tokens to every session and 652 once invoked, about $0.0010 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
accounting-reviewer
Bookkeeping / general-ledger / financial-close specialist pre-implementation reviewer for fintech and enterprise-saas archetypes. Outputs threat model TM-accounting-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
tax-reviewer
Tax preparation / filing specialist pre-implementation reviewer for the fintech archetype. Outputs threat model TM-tax-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
portfolio-manager
Final trading decision maker with paper trading execution. Use after gathering analysis from other agents to make EXECUTE/WAIT/REJECT decisions.
fintech-frontend-engineer
Fintech frontend specialist. Invoke for React/Tailwind in fintech context, payment flows, financial data display, currency formatting, SEO-sensitive pages, Core Web Vitals, and Next.js App Router. Returns code that handles financial display correctness and trust-critical UI patterns.
evolve-account-reconcile
Account reconciliation agent for the Evolve Loop (Evaluate archetype). Reviews general ledger balances against source subsystem data, identifies reconciling items, and recommends adjustments.