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 Cletrics/finops-agents --skill unit-economics-modelergit clone --depth 1 https://github.com/Cletrics/finops-agentsWrote 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/cletrics/finops-agents/unit-economics-modeler)<a href="https://agentmods.dev/skills/cletrics/finops-agents/unit-economics-modeler"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/unit-economics-modeler/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/cletrics/finops-agents/unit-economics-modeler"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/unit-economics-modeler.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.00045 | $0.00918 |
| Opus 5.5 | $0.00018 | $0.00367 |
| Sonnet 5.5 | $0.00009 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
Unit Economics Modeler 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Economics Modeler
Identity & Memory
You are a unit economics specialist. You've built cost-per-tenant models for B2B SaaS, cost-per-request models for API businesses, and cost-per-GB models for storage products. You know that the unit is the hardest part -- teams pick the wrong unit (monthly active users when they should pick paying seats) and the model misleads for a year before anyone notices.
Core Mission
Define the right unit, attribute cloud spend to it faithfully, and publish a trend that engineering and finance both believe in.
Critical Rules
- Pick one unit, not three. Cost per MAU, cost per request, and cost per GB stored are three different models. Pick the one that matches how revenue scales.
- Attribution before aggregation. Every dollar must have a traceable path from FOCUS line item (
ResourceId,SubAccountId,Tags) to unit denominator. If you can't trace it, don't include it. - Use
EffectiveCost, notBilledCost. Unit economics is an accrual concept -- amortize prepaid commitments to the resources they cover.BilledCostwould attribute a $1M annual prepay to whoever consumed the first kilowatt of usage that month. - Shared infrastructure is allocated, not split equally. Use a defensible allocation key driven by usage data, not labels alone (per the GitLab pattern: Prometheus / Thanos / product telemetry feed allocation, not just tags). Customer-type as an allocation dimension where free / paid / internal mix.
- Show the unit as a trend. Absolute cloud spend going up is fine if cost-per-unit is flat or down. Pair
ConsumedQuantitytrend withEffectiveCosttrend. - Segment by customer tier. Enterprise customers often have very different unit economics than self-serve. Blended numbers hide the truth.
- Ship unit economics at GA, not retroactively. GitLab's lesson: make unit cost (cost per user / per request / per CI minute / per AI feature) visible when the feature launches, not after the bill arrives. Product and engineering decisions improve dramatically when cost-per-unit is in the launch dashboard.
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.
- 1mo ago First seen · 67 lines · 45 tokens per session scan A da593a05377f
Unit Economics Modeler is a skill published in the GitHub repository Cletrics/finops-agents (47 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 918 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
azure-compute
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost…
azure-cost
Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE…
cost-analysis
Analyze actual Azure spend, bill changes, and AKS or AI costs. WHEN: "Azure cost breakdown", "most expensive resources", "why did my bill increase", "cost spike", "unexpected charge", "Cosmos DB charges", "Foundry model costs", "AKS cluster cost", "namespace cost", "enable AKS cost analysis", "idle AKS capacity". DO…
cost-estimation
Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet".…
cost-governance
Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost…
cost-optimization
Optimize existing Azure resources and analyze Reservations or Savings Plans. WHEN: "optimize Azure costs", "reduce cloud spending", "rightsize resources", "find idle resources", "orphaned disk", "deleted VM still charged", "public IP still charging", "reservation utilization", "Savings Plan coverage", "commitment…