letscooktech-studioletscooktech-studio/ai-engineering-arsenal/skills/cost-explosion-detector/SKILL.mdcost-explosion-detector
Skill7 starsChanged 6 days agoMITView on GitHub
Detect and prevent cloud, SaaS, data, and AI cost escalation using billing, usage, architecture, and growth evidence. Use for FinOps reviews, budget variance, pricing changes, AI inference costs, or pre-scale cost design.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- letscooktech-studio/outcomelabword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- letscooktech-studio/outcomelab★ 7100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agentic-skill-pack-integratorSkill
- ai-agent-architecture-reviewerSkill
- ai-search-optimizerSkill
- competitor-analyzerSkill
- cto-operating-systemSkill
- database-architectSkill
- nextjs-production-architecture-reviewerSkill
- nvidia-accelerated-ai-systems-operatorSkill
- production-ai-saas-builderSkill
- production-risk-labSkill
- security-auditorSkill
- seo-auditorSkill
- startup-validatorSkill
- supabase-production-auditorSkill
- system-architectSkill
- technical-debt-hunterSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Do not recommend changes that break SLOs without an explicit trade-off approval.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cost Explosion Detector
Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.
Trace spend to its technical and commercial drivers, then install guardrails before the next bill does it for you.
Workflow
- Reconcile invoice, usage, tags, owners, environments, commits/releases, and business volume for the same time window.
- Decompose spend into fixed, variable, step-function, and waste categories. Model unit cost per customer, request, workload, or token.
- Detect high-growth drivers, idle or oversized resources, egress, retry storms, storage retention, pricing-plan drift, and uncapped AI loops.
- Rank interventions by savings confidence, risk, payback, engineering effort, and reversibility.
- Define budget alerts, quotas, anomaly thresholds, allocation tags, and a weekly ownership cadence.
Output contract
Return a spend baseline, driver tree, forecast with assumptions, prioritized savings register, implementation plan, and controls.
Quality gates
- Separate realized savings from forecasts.
- Do not recommend changes that break SLOs without an explicit trade-off approval.
- Make every cost claim traceable to billing or usage evidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.