foutoucour/cost-optimization
.claude/skills/finops/cost-optimization/SKILL.md
Review infrastructure code for cloud cost optimization opportunities including rightsizing, auto-scaling, reserved instances, spot instances, and storage tiering.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add foutoucour/guitar-match cost-optimizationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 12:36 AM56.0s1 file scanned
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
- Scan IaC files: Terraform, CloudFormation, Kubernetes manifests, Helm charts.
- Identify resource specifications: instance types, storage classes, replica counts, auto-scaling configs.
- Compare against optimization patterns listed below.
What to Check
- Oversized instances: flag instances larger than
m5.large/e2-standard-4unless the workload justifies it (GPU, high-memory). Flag any instance with CPU request < 25% of instance capacity. - Missing auto-scaling: fixed
desired_capacityorreplicaswithout 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.
Related Skills
foutoucour/value-prioritization
data-ai
VerifiedTrustedCommunity
Data-driven backlog prioritization using WSJF, RICE, value/effort matrix, and dependency analysis.
SKILL.mdUpdated Apr 16, 2026
foutoucour/test-generator
development
VerifiedTrustedCommunity
Generate unit and integration tests for project code. Use when new code is written or test coverage needs improvement.
SKILL.mdUpdated Apr 16, 2026
foutoucour/test-check
testing
VerifiedTrustedCommunity
For each modified function, find or create its test, run it, and update it only if the function contract changed intentionally. Never silently adjust tests to make failures disappear.
SKILL.mdUpdated Apr 16, 2026
foutoucour/terraform-review
development
VerifiedTrustedCommunity
Review Terraform code for module structure, state management, provider versioning, security, and operational best practices.
SKILL.mdUpdated Apr 16, 2026