← ClaudeAtlas

aws-cost-auditlisted

Use when a user wants to audit, understand, reduce, or optimize their AWS bill or cloud costs, finding idle, unused, or orphaned resources, rightsizing over-provisioned compute, checking Savings Plans / Reserved Instance coverage, NAT gateway and data-transfer costs, S3 storage and lifecycle, CloudWatch log retention, untagged or unexplained spend, per-resource cost attribution ("what is this costing me and why"), or building a savings plan or cost dashboard. Triggers include "AWS bill too high", "cut/lower AWS costs", "FinOps", "Cost Explorer", "where is my money going", "unused AWS resources", and "cloud cost audit".
Aboudjem/aws-cost-audit-skill · ★ 0 · DevOps & Infrastructure · score 75
Install: claude install-skill Aboudjem/aws-cost-audit-skill
# AWS Cost Audit ## Overview Audit a **live AWS account** the way a careful FinOps engineer would: attribute every dollar, find waste, and produce an **evidence-backed savings plan** with confidence levels and **reversible, gated actions**, for *anyone's* account, with **zero hardcoded prices** and zero secrets. **Core principle:** every number is verified against a primary source before it is stated, and nothing destructive runs unless it is proven-unused, reversible, tested, and certain. A claim you did not verify is not a finding, it is a guess, and guesses do not ship. This skill targets **Claude Code** (it shells out to the AWS CLI). Work **read-only by default**; treat any change as gated (see below). ## The Iron Laws (non-negotiable) These five laws exist because, without them, agents reliably fail in specific ways (see `references/why-these-laws.md` for the recorded baseline). Violating the letter of a law violates its spirit, so do not look for loopholes. 1. **No unverified price. Ever.** Never state a unit price, a monthly cost, or a "$X saved" figure from memory. Every dollar figure must come from BOTH (a) the **live unit price** for the user's exact Region (AWS Price List Query API or the service's pricing page) and (b) the user's **actual usage** (Cost Explorer / CUR). Always show: `unit price → math → source`. **Never hardcode a price in this skill, a script, or a report.** Prices change and are Region-specific; memorized prices are how two