Enterprise Cost Governance
Use when the user asks about cloud cost governance: tagging policy, cost allocation, showback or chargeback, budgets and alerts, cost anomaly detection or unit cost reporting. Produces a cost governance model with owners and controls. Not for hands-on cloud cost optimization (use devops-finops) or capacity forecasts (use enterprise-capacity-planning).
Install
npx skills add j4flmao/agent-skills --skill enterprise-cost-governancegit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/enterprise/cost-governance ~/.claude/skills/enterprise-cost-governancePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cost Governance Agent ## Purpose Implements cloud cost governance frameworks including allocation, budgeting, chargeback/showback, anomaly detection, and optimization. ## Framework/Methodology ### GOVERN-COST Framework A six-pillar framework for systematic cloud cost governance: Pillar 1 - Governance Structure: Define cost center hierarchy, assign budget owners, establish approval gates. Create a Cloud Cost Council with representatives from engineering, finance, and product. Pillar 2 - Observability: Implement real-time cost visibility through native cloud tools and third-party platforms. Build dashboards per cost center, service, and resource type. Track unit economics (cost per transaction, per user, per API call). Pillar 3 - Validation: Enforce tagging policy through policy-as-code. Use preventive controls (SCPs, organization policies) to block non-compliant resource creation. Implement detective controls (scheduled compliance scans). Pillar 4 - Enforcement: Configure budget alerts at graduated thresholds. Implement automated actions (stop non-critical resources, send notifications, create tickets) when budgets are exceeded. Pillar 5 - Remediation: Run recurring optimization workflows. Identify idle resources, right-size over-provisioned instances, purchase commitments for stable workloads. Track savings with auditable trail.
Details
- Skill name
enterprise-cost-governance- Repository
- j4flmao/agent-skills
- Path
skills/enterprise/cost-governance/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Enterprise Cost Governance skill do?
Use when the user asks about cloud cost governance: tagging policy, cost allocation, showback or chargeback, budgets and alerts, cost anomaly detection or unit cost reporting. Produces a cost governance model with owners and controls. Not for hands-on cloud cost optimization (use devops-finops) or capacity forecasts (use enterprise-capacity-planning).
How do I install the Enterprise Cost Governance skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill enterprise-cost-governance. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Enterprise Cost Governance popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Enterprise Itil Service Mgmt
45j4flmao/agent-skills
Use when the user asks about ITIL 4, ITSM, service desk, incident, problem and change management practices, CAB, service catalog or service level management. Produces ITIL practice design and process flows. Not for on-call engineering incident response (use devops-incident-response) or SLO math (use enterprise-sla-management).
Docker Patterns
45j4flmao/agent-skills
Use when the user asks to write a Dockerfile, a multi-stage Dockerfile for a Node, Python or Go service, Docker Compose, .dockerignore, non-root containers, layer caching, BuildKit cache mounts, or image healthchecks. Produces small, secure Dockerfiles and Compose files. Not for container internals like cgroups (use docker-internals) or Kubernetes manifests (use cloud-native-kubernetes-patterns).
Github Actions
45j4flmao/agent-skills
Use when the user asks for a GitHub Actions workflow to test and deploy on push, reusable workflows, composite actions, matrix builds, GITHUB_TOKEN permissions, OIDC to a cloud, self-hosted runners, or caching. Produces secure workflow YAML with pinned actions. Not for vendor-neutral pipeline design (use cicd-pipeline) or GitLab CI (use devops-gitlab-ci).
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.