Infra Cost Guard

Infra Cost Guard

Prevents surprise cloud bills by estimating cost before apply and reminding about teardown when expensive resources are running.

1. Detect expensive resources in the plan

After terraform plan produces output, scan it for these resource types:

Azure

| Resource type | Approx cost | |---|---| | azurerm_firewall Standard SKU | ~$1.10–1.30/hr (~$26/day) | | azurerm_firewall Premium SKU | ~$2.50/hr | | azurerm_application_gateway WAF_v2 | ~$0.35/hr + data | | azurerm_nat_gateway | ~$0.045/hr + data | | azurerm_virtual_machine — check size: B-series

Confirm: these resources will accrue charges until destroyed. Teardown: terraform destroy -auto-approve (from )

Do **not** block apply — this is informational. State the teardown command
explicitly so it can be copy-pasted.

## 3. Write a teardown reminder

After a successful `terraform apply`, write a teardown note to the project's
run-log:

```markdown
## Teardown reminder — 
Resources running since apply: ~$/hr accruing.
Stop charges: `terraform destroy -auto-approve` from ``
Estimated charge if left running 24h: ~$

4. Live resource cost check (without a plan)

If asked to estimate cost for already-running resources:

Azure:

mcp__claude-skills-cli__run_command {
  cli: "az",
  args: ["resource", "list", "--resource-group", "", "--output", "json",
         "--query", "[].{name:name,type:type,sku:sku}"]
}

Match the returned types against the table in section 1.

AWS:

mcp__claude-skills-cli__run_command {
  cli: "aws",
  args: ["ce", "get-cost-and-usage", "--time-period",
         "Start=,End=",
         "--granularity", "DAILY", "--metrics", "BlendedCost"]
}

GCP:

mcp__claude-skills-cli__run_command {
  cli: "gcloud",
  args: ["billing", "accounts", "list"]
}

5. Rules

• Always emit the teardown command alongside any cost warning — it reduces

the friction of stopping resources.

• Do not refuse to deploy expensive resources; the user decides. Your job

is to make costs visible before apply, not to block work.

• Prices are estimates. For exact rates use the cloud provider's pricing

calculator or Cost Management tools.

• For long-running demo/test environments (firewall, K8s, databases), suggest

scheduling a destroy or setting an auto-shutdown policy.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: sergeyitaly
• Source: sergeyitaly/claude-skill-deployer
• License: MIT

Install and usage instructions live in the source repository linked above.