About cloud-cost-management
A skill for planning and improving cloud spending, aimed at teams managing infrastructure costs. It covers cost analysis, allocation, forecasting and optimization practices, with guides spanning AWS, Terraform, Azure and GCP.
Key features
- 01Cloud spending analysis
- 02Compute and database optimization
- 03Storage and data transfer cost reduction
- 04Reserved capacity and Spot planning
- 05Cost allocation and budget alerts
Use cases
- 01Review service spending with AWS Cost Explorer
- 02Right-size compute instances
- 03Plan reserved capacity for stable workloads
- 04Track costs by allocation and budget alerts
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ aj-geddes/ useful-ai-prompts --skill cloud-cost-managementAfter installing, type/cloud-cost-managementin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/aws-cost-optimization-with-aws-cli.mdazure-cost-management.mdcost-monitoring-dashboard.mdgcp-cost-optimization.mdterraform-cost-management-configuration.mdscripts/validate-config.shtemplates/config-starter.yamlDetails
From the project READMECloud Cost Management
Table of Contents
Overview
Cloud cost management involves monitoring, analyzing, and optimizing cloud spending. Implement strategies using reserved instances, spot pricing, proper sizing, and cost allocation to maximize ROI and prevent budget overruns.
When to Use
- Reducing cloud infrastructure costs
- Optimizing compute spending
- Managing database costs
- Storage optimization
- Data transfer cost reduction
- Reserved capacity planning
- Chargeback and cost allocation
- Budget forecasting and alerts
Quick Start
Minimal working example:
# Enable Cost Explorer
aws ce get-cost-and-usage \
--time-period Start=2024-01-01,End=2024-01-31 \
--granularity MONTHLY \
--metrics "UnblendedCost" \
--group-by Type=DIMENSION,Key=SERVICE
# List EC2 instances for right-sizing
aws ec2 describe-instances \
--query 'Reservations[*].Instances[*].[InstanceId,InstanceType,State.Name,LaunchTime,Tag]' \
--output table
# Find unattached EBS volumes
aws ec2 describe-volumes \
--filters Name=status,Values=available \
--query 'Volumes[*].[VolumeId,Size,State,CreateTime]'
# Identify unattached Elastic IPs
aws ec2 describe-addresses \
--query 'Addresses[?AssociationId==null]'
# Get RDS instance costs
aws rds describe-db-instances \
--query 'DBInstances[*].[DBInstanceIdentifier,DBInstanceClass,StorageType,AllocatedStorage]'
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| AWS Cost Optimization with AWS CLI | AWS Cost Optimization with AWS CLI |
| Terraform Cost Management Configuration | Terraform Cost Management Configuration |
| Azure Cost Management | Azure Cost Management |
| GCP Cost Optimization | GCP Cost Optimization |
| Cost Monitoring Dashboard | Cost Monitoring Dashboard |
Best Practices
✅ DO
- Use Reserved Instances for stable workloads
- Implement Savings Plans for flexibility
- Right-size instances based on metrics
- Use Spot Instances for fault-tolerant workloads
- Delete unused resources regularly
- Enable detailed billing and cost allocation
- Monitor costs with CloudWatch/Cost Explorer
- Set budget alerts
- Review monthly cost reports
❌ DON'T
- Leave unused resources running
- Ignore cost optimization recommendations
- Use on-demand for predictable workloads
- Skip tagging resources
- Ignore data transfer costs
- Forget about storage lifecycle policies
Comments
Markdown supported