On one Terraform file it found 8 standing charges: one NAT gateway per AZ ($98.55 a month across three before any GB), EKS 1.33 past standard support ($365 more a month), public IPv4 on launch ($3.65 per instance), gp2, logs that never expire — each with the fix line.

Who it’s for
For teams that run AWS or Azure through Terraform and pay the monthly bill.

What breaks, and when
These charges are written into code, so they repeat every month: one NAT gateway per AZ is $98.55 a month across three before any traffic, and EKS 1.33 past standard support adds $365 a month per cluster.

What you get
• 27 rules for charges fixed in code: public IPv4, idle Elastic IPs, NAT…
• Every finding carries the list price as written in the rule and a fix; Claude…

See it first
The real output of the bundled example is on getreadystack.com/skills/terraform-cost-lint/ — free, no sign-up, so you see what it finds before you pay.

Install in 30 seconds
Unzip into ~/.claude/skills/, then ask Claude Code: “review our Terraform for standing costs”. Needs Node 16+.

What it does not do
It works offline and does not read your cloud account or bill.

FAQ
Q: How is this different from asking Claude without the skill?
A: The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of guessing from memory.
Q: How do I get the files?
A: In your Whop library after paying: the lesson “terraform-cost-lint.zip”.