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/Dokkabei97/forged-claude-codeWrote 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/commands/dokkabei97/forged-claude-code/unit-economics)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/unit-economics"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/unit-economics.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.00028 | $0.00844 |
| Opus 5 | $0.00014 | $0.00422 |
| Sonnet 5 | $0.00006 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
unit-economics 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 7d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/unit-economics - Unit Economics Calculator
Triggers
- When assessing business model health
- Before fundraising to present financials
- When evaluating marketing channel efficiency
Usage
/unit-economics
/unit-economics --simulate # Run improvement scenarios
/unit-economics --arpu 50 --churn 5 # Direct input
Behavioral Flow
Phase 1: Input Collection
Required:
- Monthly revenue per customer (ARPU): $[N]
- Monthly churn rate: [N]%
- Customer acquisition cost (CAC): $[N]
Optional:
- Gross margin: [N]%
- Monthly growth rate: [N]%
- Expansion revenue rate: [N]%
Phase 2: Calculate Metrics
LTV = ARPU × Gross Margin / Churn Rate
Payback Period = CAC / (ARPU × Gross Margin)
LTV/CAC Ratio = LTV / CAC
Example:
ARPU: $50/month, Churn: 5%/month, CAC: $200, Margin: 80%
LTV = $50 × 0.80 / 0.05 = $800
Payback = $200 / ($50 × 0.80) = 5 months
LTV/CAC = $800 / $200 = 4.0x
Phase 3: Health Assessment
# Unit Economics Report
## Core Metrics
| Metric | Value | Benchmark | Status |
|--------|-------|-----------|--------|
| ARPU | $[N]/mo | - | - |
| Churn Rate | [N]%/mo | <5% SaaS | 🟢/🟡/🔴 |
| CAC | $[N] | - | - |
| LTV | $[N] | - | - |
| **LTV/CAC** | **[N]x** | >3x | 🟢/🟡/🔴 |
| **Payback** | **[N] mo** | <12 mo | 🟢/🟡/🔴 |
| Gross Margin | [N]% | >70% SaaS | 🟢/🟡/🔴 |
## Health Score
🟢 **Healthy** (LTV/CAC > 3, Payback < 12mo)
🟡 **Improving** (LTV/CAC 1-3, Payback 12-18mo)
🔴 **Unsustainable** (LTV/CAC < 1, Payback > 18mo)
## Improvement Scenarios
| Scenario | Change | New LTV/CAC | Impact |
|----------|--------|-------------|--------|
| Cut churn by 1% | [N]% → [N]% | [N]x | +$[N] LTV |
| Increase ARPU 20% | $[N] → $[N] | [N]x | +$[N] LTV |
| Reduce CAC 25% | $[N] → $[N] | [N]x | Faster payback |
## Highest-Impact Lever
[Which change gives the biggest LTV/CAC improvement]
Tool Coordination
- Write: Generate unit economics report
Boundaries
Will:
- Calculate LTV, CAC, LTV/CAC, payback period
- Assess health against SaaS benchmarks
- Run improvement simulations
- Identify highest-impact levers
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.
- 7d ago First seen · 101 lines · 28 tokens per session scan A 7c1d2eac84c8
unit-economics is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 844 once invoked, about $0.0001 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 commands, from other repositories
seed
Typed project incubator — guided ideation through graduation into buildable projects.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
fix
Universal debugging and fix application with semantic code analysis.