cloud-cost-governance

Enforce tagging, budgets, and lifecycle policies for cloud cost governance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/prapanch/agent-coda --skill cloud-cost-governance-prapanch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-cost-governance
Source: https://github.com/prapanch/agent-coda/tree/main/infra/cloud-cost-governance
Command: npx skills add https://github.com/prapanch/agent-coda --skill cloud-cost-governance-prapanch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloud cost overruns often happen invisibly—through untagged resources, missing budgets, and steady waste—until bills arrive and anomalies are already expensive to unwind.

Core Features & Use Cases

  • Mandatory cost attribution via tagging: Enforces required metadata (Environment, Team, Service, Owner, CostCenter) so resources map cleanly to ownership and reporting.
  • Budgets, alerts, and early intervention: Defines guardrails before provisioning and sets alert thresholds (e.g., 50%, 80%, 100%, 120%) with agreed actions.
  • Lifecycle governance to prevent “zombie” spend: Implements right-sizing and time-based cleanup for dev/preview/test/log data and snapshot retention.
  • Structured monthly review process: Provides a repeatable review template to identify top cost drivers, anomalies, optimization opportunities, and unused resources.

Quick Start

Use the cloud-cost-governance skill to audit your current cloud inventory, verify required tags and budgets, then produce a prioritized list of right-sizing and lifecycle changes to cut monthly spend.

Frequently Asked Questions about cloud-cost-governance

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

FAQPage Schema
How do I stop untagged cloud resources from causing invisible cost overruns?

Cloud cost governance prevents invisible overruns by enforcing mandatory tagging schemas like Environment, Team, and CostCenter. This ensures resources map cleanly to ownership and reporting, making accumulated spend visible before billing anomalies become expensive to unwind.

What is the best way to set up cloud budgets and alerts for early intervention?

Define cloud budgets with specific alert thresholds at 50%, 80%, 100%, and 120% of limits, paired with agreed-upon actions. This proactive approach establishes guardrails before provisioning, triggering early intervention rather than reacting to unexpected bills.

How do I eliminate zombie cloud spend from unused dev and test environments?

Eliminate zombie cloud spend by implementing lifecycle governance with right-sizing and time-based cleanup policies. Apply retention rules to dev, preview, and test log data or snapshots to automatically remove unused resources and prevent continuous waste.

How do I perform a structured monthly cloud cost review to find optimization opportunities?

Use a repeatable monthly review template to identify top cost drivers, billing anomalies, and unused resources. This structured process highlights right-sizing and data-transfer awareness opportunities to systematically optimize monthly cloud spend.

Can I use Infracost for pre-deployment cloud cost estimation before provisioning?

Yes, apply cloud cost governance to pre-deployment cost estimation decisions using Infracost. This requires concrete lifecycle policies and budget thresholds to evaluate infrastructure provisioning impacts across environments and services before resources are created.