hoangminhung/devops-ai-kit / claude/skills/finops
finops
VerifiedCloud cost-control standards — cost estimation gates for Terraform changes (Infracost), NAT and data-transfer costs, orphaned resources, Kubernetes right-sizing, storage and log-ingestion costs (including Azure Log Analytics), and non-production savings. Use whenever a change adds or resizes cloud resources, when designing networking that affects data transfer, when reviewing monitoring/logging volume, or when the user asks why the bill is high or how to cut costs.
FinOps & cost control standards
1. Estimate before you create
- SHOULD Terraform changes that affect cost: run
infracost diffand put the number (monthly increase / decrease) in the plan. - CONTEXT Automatic blocking thresholds in CI (for example, an increase > 200 USD/month needs Lead / Finance approval and no auto-merge) follow the organization's policy.
- SHOULD Costs that are hard to see must be estimated in words if the tool cannot calculate them: data transfer, log ingestion, object storage requests, number of snapshots.
2. Network & data transfer
- SHOULD Non-prod: one shared NAT Gateway (or a NAT instance) instead of one per AZ.
- SHOULD For large data volumes, prefer keeping internal traffic in the same zone (topology-aware routing) to avoid cross-AZ fees.
- SHOULD AWS: use Gateway Endpoints for S3 / DynamoDB (free) instead of going through NAT.
- SHOULD Use cross-region backup / replication only when the RPO / RTO really needs it; write the cost in the ADR.
3. Logs & metrics (often a surprise cost)
- SHOULD Azure: Log Analytics / Container Insights charge per GB ingested. Collect only the namespaces / tables you need (data collection rule), consider a cheaper log plan for logs that are rarely queried, and set retention on purpose.
- SHOULD Self-hosted (Loki / Prometheus): the cost is in storage and replication. Size = ingest volume × retention × replication factor (of the app and of the storage, see
k8s-storage). - MUST Do not turn on debug logs in production without a time to turn them off.
4. Kubernetes
- SHOULD Requests decide how many nodes you pay for. Regularly compare requests with real usage (
kubectl top, Prometheus metrics) and adjust them. Inflated requests are the most common waste. - CONTEXT Spot / preemptible nodes for workloads that can handle interruptions; on-demand for infrastructure node pools.
- CONTEXT Stop dev clusters outside working hours (for example
az aks stopfor a dev AKS) if the team agrees. - CONTEXT OpenCost / Kubecost when you need to split cost by namespace / team.
5. Orphaned resources — scan regularly
- Disks not attached to a VM / node (Azure Managed Disk, EBS).
- Public IPs / Elastic IPs not assigned.
- Old snapshots past retention.
- Load Balancers with no healthy backend.
- PVs in
Releasedstate because ofreclaimPolicy: Retain: review them, then delete in a controlled way. Do not delete them automatically, because they may hold data that must be kept.
6. Long-term commitments
- CONTEXT Reserved Instances / Savings Plans / Azure Reservations for a stable base load for ≥ 1 year. Decide based on at least a few months of real usage.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |