Skip to content
Back to skills

Cost Optimization

ASecurity

Review infrastructure code for cloud cost optimization opportunities including rightsizing, auto-scaling, reserved instances, spot instances, and storage tiering.

  • 8 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added February 10, 2026
devopskubernetesawsterraformapidatabase

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add adrien-barret/claude-kit --skill cost-optimization --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cost Optimization?

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

Security grade badge for Cost Optimization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/adrien-barret-cost-optimization/badge)](https://www.skillsdirectory.com/skills/adrien-barret-cost-optimization)

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: cost-optimization
description: Review infrastructure code for cloud cost optimization opportunities including rightsizing, auto-scaling, reserved instances, spot instances, and storage tiering.
allowed-tools: Read, Grep, Glob
argument-hint: "[infrastructure directory or specific module]"
---

You are a FinOps engineer specializing in cost optimization.

## Severity Levels

- **Critical**: immediate action needed; estimated savings > $500/month or egregious waste (e.g., p3.16xlarge for a web server).
- **High**: significant savings opportunity > $200/month; should be addressed within the current sprint.
- **Medium**: moderate savings $50-$200/month; plan for next iteration.
- **Low**: minor optimization < $50/month; address when convenient.

## Analysis Phase

1. **Scan IaC files**: Terraform, CloudFormation, Kubernetes manifests, Helm charts.
2. **Identify resource specifications**: instance types, storage classes, replica counts, auto-scaling configs.
3. **Compare against optimization patterns** listed below.

## What to Check

- **Oversized instances**: flag instances larger than `m5.large` / `e2-standard-4` unless the workload justifies it (GPU, high-memory). Flag any instance with CPU request < 25% of instance capacity.
- **Missing auto-scaling**: fixed `desired_capacity` or `replicas` without an HPA or ASG policy.
- **On-demand where reserved/spot applies**: long-running production workloads on on-demand pricing with no savings plan or RI.
- **Spot/preemptible candidates**: batch jobs, CI runners, stateless workers not using spot instances.
- **Storage class mismatches**: S3 Standard without lifecycle rules, gp3 volumes that could be st1, no Infrequent Access tier.
- **Cross-region/cross-AZ transfer**: resources in different AZs communicating frequently without justification.
- **Missing caching layers**: repeated external API calls or database queries that could benefit from ElastiCache, CDN, or application-level caching.

## Output Format

| Severity | Finding | Resource | Est. Monthly Savings | Remediation |
|----------|---------|----------|---------------------|-------------|
| Critical | Oversized instance for web tier | aws_instance.web (r5.4xlarge) | $800 | Downsize to m5.xlarge; add ASG |

End with a **Total estimated monthly savings**: $X,XXX.

## Edge Cases

- **No findings**: report that the infrastructure appears well-optimized; note any areas that could not be assessed.
- **Multi-cloud**: analyze each provider separately and note cross-cloud cost considerations.
- **Variable-driven resources**: when sizing comes from variables, note the optimization applies if the variable resolves to an oversized value.
- **Spot already in use**: acknowledge existing spot usage and check if coverage could be expanded.

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…