Skip to content
Back to skills

Ai Unit Economics

ASecurity

AI unit-economics discipline — auto-activates when evaluating whether AI spend is worth it, pushing from tokens and requests to cost-per-successful-outcome

  • 29 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
ai-agentsgo

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add alexclowe/awesome-claude-cowork-plugins --skill ai-unit-economics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ai Unit Economics?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ai Unit Economics
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alexclowe-ai-unit-economics/badge)](https://www.skillsdirectory.com/skills/alexclowe-ai-unit-economics)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ai-unit-economics
description: AI unit-economics discipline — auto-activates when evaluating whether AI spend is worth it, pushing from tokens and requests to cost-per-successful-outcome
---

You hold the unit-economics discipline for AI spend conversations. When the user is evaluating AI cost or value, apply these rules automatically.

## The core move

Tokens, requests, and monthly bills are inputs. The decision-grade number is **cost per successful task** — total workflow cost divided by outcomes that actually met the quality bar. Whenever a conversation stalls on "is this expensive?", reframe to "what does one good outcome cost, and what did it cost before AI?"

## Numerator discipline

The full cost of a successful task includes:
- The model calls that produced it — AND the retries and failed attempts along the way
- Guardrail, evaluation, and monitoring calls riding on the workflow
- The amortized slice of any subscription, credit pool, or reserved capacity it consumes
- Human review time where it's a structural part of the loop (note it even if unpriced)

## Denominator discipline

- Only outcomes that met the stated quality bar count as successes
- Outputs that needed substantial human rework are partial successes at best — pick a convention and keep it consistent
- If nobody has defined "successful," that's the first finding — propose a definition before optimizing anything

## Interpretation rules

- A missing retry/failure rate means the computed number is a FLOOR — always label it
- Cost-per-success comparisons across models are only valid at the same quality bar; a cheaper model that fails more is often more expensive per success
- Watch the denominator when costs "improve" — falling cost per task with falling task quality is a regression wearing a trend line
- Unit economics justify scale decisions; run-rate totals justify budget decisions — keep the two arguments separate

## The counterfactual

The strongest version of the analysis includes what the task cost before AI (labor minutes × loaded rate, vendor fee, or queue time). Without a counterfactual, cost-per-success describes the spend; with one, it justifies or kills it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…