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.
npx skills add w95/awesome-claude-corporate-skills --skill unit-economicsgit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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/skills/w95/awesome-claude-corporate-skills/unit-economics)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/unit-economics"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/unit-economics/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/skills/w95/awesome-claude-corporate-skills/unit-economics"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/unit-economics.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.00000 | $0.01061 |
| Opus 5 | $0.00000 | $0.00531 |
| Sonnet 5 | $0.00000 | $0.00212 |
| Haiku 4.5 | $0.00000 | $0.00106 |
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 12d 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.
This is a copy
91% identical to unit-economics — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Economics Analysis
description: Analyze unit economics for PE targets — ARR cohorts, LTV/CAC, net retention, payback periods, revenue quality, and margin waterfall. Essential for software/SaaS, recurring revenue, and subscription businesses. Use when evaluating revenue quality, building a cohort analysis, or assessing customer economics. Triggers on "unit economics", "cohort analysis", "ARR analysis", "LTV CAC", "net retention", "revenue quality", or "customer economics".
Workflow
Step 1: Identify Business Model
Determine the revenue model to tailor the analysis:
- SaaS / Subscription: ARR, net retention, cohorts
- Recurring services: Contract value, renewal rates, upsell
- Transaction / usage-based: Revenue per transaction, volume trends, take rate
- Hybrid: Break down by revenue stream
Step 2: Core Metrics
ARR / Revenue Quality
- ARR bridge: Beginning ARR → New → Expansion → Contraction → Churn → Ending ARR
- ARR by cohort: Vintage analysis — how does each annual cohort retain and grow?
- Revenue concentration: Top 10/20/50 customers as % of total
- Revenue by type: Recurring vs. non-recurring vs. professional services
- Contract structure: ACV distribution, multi-year %, auto-renewal %
Customer Economics
- CAC (Customer Acquisition Cost): Total S&M spend / new customers acquired
- LTV (Lifetime Value): (ARPU × Gross Margin) / Churn Rate
- LTV:CAC ratio: Target >3x for healthy businesses
- CAC payback period: Months to recover acquisition cost
- Blended vs. segmented: Break down by customer segment (enterprise vs. SMB vs. mid-market)
Retention & Expansion
- Gross retention: % of beginning ARR retained (excludes expansion)
- Net retention (NDR): % of beginning ARR retained including expansion
- Logo churn: % of customers lost
- Dollar churn: % of revenue lost (often different from logo churn)
- Expansion rate: Upsell + cross-sell as % of beginning ARR
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.
- 12d ago First seen · 93 lines · 0 tokens per session scan A 5d2c8b87a647
unit-economics is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,061 tokens. A static security scan graded it A with 0 findings. It is 91% identical to unit-economics, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
design-por-referencia
Use when a landing page, marketing site, or hero section looks generic/AI-made ("cara de vibe coding") and needs a $10k-agency-level redesign, or when building a new landing from scratch. Triggers - "o site ficou com cara de IA", "quero uma landing premium", "redesenha a landing", "faz o site baseado em [site de…
lighthouse-95
Use when a website must score 95+ in every Lighthouse category (Performance, Accessibility, Best Practices, SEO), when scores are stuck below target, or when diagnosing poor FCP, LCP, TBT, or CLS on a deployed site.
seo-validate
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability. Triggers: SEO, meta tags, Schema.org, hreflang, LCP, INP, CLS, Core Web Vitals, sitemap, crawlability.
debug
Systematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
research-mastery
Hierarchical retrieval: KB → MCP/Context7 → web. Triggers: research, fact-check, verify, synthesize, cross-reference, multi-source, cite sources.