audit-aws-costs

Audits AWS account spending and resource provisioning via CloudTrail and Cost Explorer data.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill audit-aws-costs-zcaceres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-aws-costs
Source: https://github.com/zcaceres/skills/tree/main/skills/audit-aws-costs
Command: npx skills add https://github.com/zcaceres/skills --skill audit-aws-costs-zcaceres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aws-cli, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill solves the problem of "cloud sprawl" and unexpected AWS bills by providing a comprehensive, read-only audit of your account's resources, recent provisioning activity, and actual spending.

Core Features & Use Cases

  • Cost Explorer Analysis: Breaks down spend by service and region to identify top cost drivers.
  • CloudTrail Sweep: Scans all enabled regions for recent write activity to pinpoint who or what provisioned resources.
  • Idle Resource Inventory: Identifies billable resources like unassociated EIPs, idle NAT gateways, and unused EBS volumes that are silently increasing your monthly bill.

Quick Start

Invoke the audit-aws-costs skill to generate a full report of your current AWS spend and identify potential cost-saving opportunities.

Frequently Asked Questions about audit-aws-costs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my AWS account for unused resources and unexpected costs?

An AWS cost audit analyzes Cost Explorer usage data, CloudTrail write events, and billable resource inventories across all enabled regions. It identifies idle resources like unassociated EIPs and unused EBS volumes that silently increase your monthly bill.

What is the best way to find out who or what provisioned resources in my AWS account?

Scanning CloudTrail write events across all enabled regions pinpoints who or what provisioned resources in your AWS account. This sweep identifies recent provisioning activity to trace the source of unexpected resource sprawl.

Do I need AWS CLI v2 and Python 3 to run a read-only AWS cost audit?

Yes, you need AWS CLI v2 configured with read-only credentials and Python 3 to run a read-only AWS cost audit. Python 3 is required for synthesizing the final spend and resource report.

How does an AWS cost audit identify idle resources like NAT gateways and EBS volumes?

An AWS cost audit identifies idle resources by analyzing billable resource inventories across all enabled regions. It specifically flags unassociated Elastic IPs, idle NAT gateways, and unused EBS volumes that increase your monthly bill.

Can I use a read-only AWS audit to break down spend by service and region?

Yes, a read-only AWS audit breaks down spend by service and region using Cost Explorer analysis. This identifies top cost drivers and provides a comprehensive view of your account spend and potential cost-saving opportunities.

What are the limitations of a read-only AWS infrastructure and cost audit?

A read-only AWS infrastructure and cost audit cannot modify or delete resources; it only provides analysis and reporting. It requires pre-configured read-only credentials and reports on current spend and provisioning state without taking corrective action.