Skip to content
/infra-costStable

Analyze cloud infrastructure costs and suggest optimizations. Finds unused resources, right-sizing opportunities, and savings.

DevOpsCloud· 2 min read

Quick import: Download the .md file and save it to .claude/commands/ (Claude Code), .cursorrules (Cursor), or paste as a system prompt in ChatGPT, Gemini, or any LLM API.

#What it does

The /infra-cost skill analyzes your cloud infrastructure spending and identifies concrete savings. It finds idle resources, recommends right-sizing, evaluates reserved capacity options, and flags cost anomalies before they become budget surprises.

#How to use

bash
/infra-cost
/infra-cost aws
/infra-cost --compare last-month

#Workflow

  1. Inventory -- Catalogs all cloud resources across providers and regions
  2. Analyze -- Measures actual utilization against provisioned capacity
  3. Identify -- Flags unused resources, over-provisioned instances, and cost spikes
  4. Recommend -- Proposes specific changes ranked by monthly savings
  5. Estimate -- Projects total savings with implementation effort for each change

#What it finds

  • Idle resources -- Unattached EBS volumes, unused Elastic IPs, stopped instances still incurring storage costs
  • Over-provisioned -- Instances running at 5% CPU, databases with 90% unused storage, oversized Lambda memory
  • Missing savings plans -- Steady-state workloads without reserved instances or committed use discounts
  • Architecture waste -- NAT Gateway charges replaceable with VPC endpoints, cross-region data transfer costs
  • Development sprawl -- Staging environments running 24/7, forgotten preview deployments

#Example

bash
> /infra-cost aws
 
# Scanning AWS account...
42 resources across 3 regions, $2,847/month current spend
 
# Findings:
SAVE $480/mo   3x RDS instances at 8% avg CPU -> downsize db.r6g.xl to db.r6g.large
SAVE $340/mo   Dev/staging environments running 24/7 -> schedule off-hours shutdown
SAVE $220/mo   12 unattached EBS volumes (840GB total) -> delete after backup
SAVE $180/mo   NAT Gateway for S3 traffic -> use VPC Gateway Endpoint (free)
SAVE $95/mo    Lambda functions at 1024MB using 180MB peak -> right-size to 256MB
SAVE $60/mo    3 unused Elastic IPs -> release
 
# Total potential savings: $1,375/month ($16,500/year)
# Implementation effort: ~4 hours
# Risk: Low (all changes reversible)
Orel Ohayon·
View all skills