Agent skill · Business & Finance

Cost Observability and Monitoring

Techniques for gaining visibility into cloud spending, attributing costs to business units, and detecting financial anomalies.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill cost-observability-amnadtaowsoam-cerebratechai-claude --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/analysis/cost-observability-amnadtaowsoam-cerebratechai-claude/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Cost Observability and Monitoring ## Overview Cost Observability is the practice of extending traditional system observability (logs, metrics, traces) to include **Financial** data. It allows engineering teams to answer not just "Is the system healthy?" but "Is the system cost-effective?". **Core Principle**: "Total spend is a vanity metric; cost per unit of work is a performance metric." --- ## 1. Key Cost Metrics to Track The goal is to move from **Macro** visibility (the bill) to **Micro** visibility (the request). | Metric | Level | Purpose | | :--- | :--- | :--- | | **Total Monthly Spend** | Executive | General budget health. | | **Cost per Service** | Engineering | Identify inefficient microservices. | | **Cost per Customer (Unit Cost)**| Product | Calculate per-account profitability. | | **Cost per Request** | Engineering | Measure efficiency of application code. | | **COGS (Cost of Goods Sold)** | Financial | The base cost to deliver the service. | --- ## 2. Cost Attribution and Tagging Strategy Attribution is impossible without consistent metadata. ### The Standard Tagging Schema Every resource should have the following "FinOps Tags": 1. **`Environment`**: (e.g., `prod`,

What's inside
Steps it walks through
  1. Overview
  2. 1. Key Cost Metrics to Track
  3. 2. Cost Attribution and Tagging Strategy
  4. The Standard Tagging Schema
  5. Enforcement Policy (Terraform/OpenTofu)
  6. 3. Cost Anomaly Detection
  7. Types of Anomalies
  8. Anomaly Alert Example (Slack/PagerDuty)
  9. 4. Application-Level Cost Tracking
  10. OpenTelemetry for Cost
  11. 5. Dashboard Templates
  12. Engineering Dashboard (Grafana)
  13. Product/Executive Dashboard
  14. 6. Tools Ecosystem
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the Cost Observability and Monitoring skill do?

Techniques for gaining visibility into cloud spending, attributing costs to business units, and detecting financial anomalies.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill cost-observability-amnadtaowsoam-cerebratechai-claude --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going