Skip to content
Conduit

skill

aws-cost-audit-skill

Ask Claude to audit your AWS bill. Every number is checked against live AWS pricing, and nothing is deleted without your say-so.

Aboudjem/aws-cost-audit-skillcommunitylistedunreviewed

Set up

Skills are installed by placing their folder where your agent loads skills.

The download comes from github.com/Aboudjem/aws-cost-audit-skill itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Oct 26, 2026

claude plugin marketplace add Aboudjem/10x
claude plugin install aws-cost-audit@10x

What it does

It is a skill for Claude Code: a Markdown instruction file, six reference documents it loads only when it needs them, and ten bash helper scripts. Claude picks it up when you ask about AWS spend.

You say "audit my AWS bill". It reads your account through the AWS CLI you already have, works out what each resource costs and why, and hands you a plan. It reads only by default. It never quotes a price from memory, and it never deletes anything on its own.

  • A spend breakdown. What you pay per service and per region, pulled live from Cost Explorer.
  • A per-resource view. What each thing costs, what it does in plain words, who made it, and when it was last used. If a fact cannot be verified it says so instead of guessing.
  • A savings plan in two halves. "Save now safely" (reversible, high confidence) kept apart from "maximum theoretical save", which needs your sign-off.

The method follows the AWS Well-Architected cost-optimization pillar and the FinOps Foundation framework, so it is not something the skill made up.

Install

Inside Claude Code, from the 10x marketplace:

claude plugin marketplace add Aboudjem/10x
claude plugin install aws-cost-audit@10x

In any other agent, through the Vercel skills CLI:

npx skills add Aboudjem/aws-cost-audit-skill

You also need the AWS CLI configured with read access to the account you want to audit. The AWS managed ReadOnlyAccess policy plus billing read is enough for the audit itself.

Skip the plugin system entirely. The skill is a directory of Markdown and shell scripts, so copying it into a directory your agent reads is enough:

git clone https://github.com/Aboudjem/aws-cost-audit-skill
mkdir -p ~/.claude/skills
cp -r aws-cost-audit-skill/skills/aws-cost-audit ~/.claude/skills/aws-cost-audit

This repo carries no marketplace manifest of its own, so claude plugin marketplace add Aboudjem/aws-cost-audit-skill will not resolve. The 10x marketplace above is the plugin path. Windows and the per-editor paths are in docs/editors.md.

Use it

1. Check the environment. doctor.sh names what is missing before an audit starts. It makes no AWS call that changes anything, it has no apply flag, and it removes the probe file it writes:

bash skills/aws-cost-audit/scripts/doctor.sh --offline
aws-cost-audit doctor

[OK]   aws CLI found: aws-cli/2.33.9 Python/3.13.12 Darwin/25.3.0 source/arm64
[SKIP] caller identity (--offline)
[OK]   jq found: jq-1.7.1-apple
[OK]   region resolves to ap-southeast-1
[OK]   output directory writable: ./cost-audit-out
[SKIP] Cost Explorer probe (opt in with --check-cost-explorer; the request is billed)

No blockers. This environment can run an audit.

2. Ask Claude. Say audit my AWS bill, or find my unused AWS resources. The skill is written to trigger on that phrasing. Tell it which profile and regions to look at if you have more than one account.

3. Read the plan. You get a report and, if you want one, an HTML dashboard. Nothing in your account changes unless you ask, and even then only after a dry run and your confirmation.

The full walkthrough, from credentials to dashboard, is in the quickstart.

What you get

  • A report. Each finding reads current $/mo -> after $/mo -> $ saved, with the evidence, a confidence level, and how to undo it. See examples/sample-report.md.
  • A dashboard, optionally. One HTML file a non-technical person can open. It pulls its font and its chart library from a CDN, so it looks right on a machine with a network. See examples/sample-dashboard.html.
  • A machine-readable findings.json, on request. findings-validate.sh checks it against a pinned structural contract, which is what makes two audits comparable instead of re-read.
  • A live price for every dollar. Unit price, the math, and the source, looked up for your region. The Price List Query API is the first stop; where a figure cannot be verified it stays marked unknown.
  • Guardrails. It reports whether you have budgets and cost-anomaly alerts, and helps you set them.

Works in your editor

AgentOne-line install
Claude Codeclaude plugin install aws-cost-audit@10x
Any of 70+ other agentsnpx skills add Aboudjem/aws-cost-audit-skill
Codex, Gemini CLI, OpenCode, Pi./install.sh codex (or gemini, opencode, pi)
VS Code with Copilot./install.sh copilot
Everything elsesee docs/editors.md

Works in Claude Code, Cursor, Codex, Copilot, Gemini CLI, and 70+ other agents through npx skills add. install.sh is the wrapper for the thirteen editor ids this repo has always supported, and it now delegates to that same CLI:

curl -fsSL https://raw.githubusercontent.com/Aboudjem/aws-cost-audit-skill/main/install.sh | bash -s codex

This plugin ships no MCP server, on purpose. It shells out to the AWS CLI you already have, so there is no extra process to run and nothing to add to an .mcp.json.

Good to know

[!IMPORTANT] It is read-only by default. It will not delete, stop, or change anything on its own. Any action is gated: the resource must be proven unused, the change must be reversible, it must pass a dry run, and you must confirm. Irreversible actions stay recommendations.

  • No prices from memory. Every dollar comes from the live AWS price for your region times your real usage. No resource price is written into a script or into a finding, and CI fails the build if one appears. The single price this repo records is Cost Explorer's own per-request API charge, which is what the audit costs to run, not the price of anything it reports on. It sits in a reference document with its AWS source.
  • Cost Explorer requests are counted and capped. The scripts route their requests through one wrapper that counts each page and refuses the one past AWS_COST_AUDIT_CE_BUDGET. An aws ce call you make yourself is outside that count.
  • It talks to AWS and to nothing else. It uses the AWS CLI credentials already on your machine, asks you for no keys, and sends your audit to no third party. The scripts need bash and the AWS CLI; findings-validate.sh also needs jq.

Learn more


Built and maintained by Adam Boudjemaa. Commands are written for AWS CLI v2. Spot a stale command or a gap? Open an issue.

↑↓ navigate openesc close