How do I install the Grafana Billing skill?

Run npx skillmds add nodnarbnitram/grafana-billing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Grafana Billing safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Grafana Billing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Grafana Billing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Grafana Billing?

nodnarbnitram (@nodnarbnitram) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Grafana Billing by nodnarbnitram — Agent Skill

Name: Grafana Billing
Rating: 4.666666666666667 (3 reviews)
Author: nodnarbnitram

File contents

Grafana Billing Metrics Skill

Query key billing metrics from Prometheus and Loki through Grafana's data source proxy API.

Quick Start

# Query both staging and prod (default)
uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py

# Query specific environment
uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --env staging
uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --env prod

# JSON output for automation
uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --json

# Filter to specific service
uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --service prometheus
uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --service loki

Environment Variables Required

GRAFANA_STAGING_API_KEY - API key for staging Grafana workspace
GRAFANA_PROD_API_KEY - API key for prod Grafana workspace

Key Metrics Captured

Prometheus

Metric	Description
Active Time Series	Current count of active series (billing dimension)
Samples/sec	Ingestion rate (DPM = samples/sec * 60)
TSDB Storage	On-disk storage bytes
Top Cardinality	Top 10 metrics by series count

Loki

Metric	Description
Ingestion Rate	GB/day being ingested
Total Bytes	Cumulative bytes received
Active Streams	Number of active log streams
Memory Chunks	Chunks held in memory

When to Use

Use this skill when the user asks about:

Observability billing or costs
Active time series counts
Prometheus cardinality analysis
Loki ingestion rates
Storage usage for metrics or logs
Comparing staging vs production usage

Instructions for Claude

Run the billing metrics script to gather current data
Present the results in a clear, formatted way
Highlight any concerning metrics (high cardinality, rapid growth)
Compare staging vs prod if both are queried
Suggest cost optimization if metrics are unusually high

Critical Rules

Always check that API keys are set before running
Use --json flag when you need to process the output programmatically
Default to querying both environments for comparison
Handle errors gracefully - missing data sources should not crash the script

---name: grafana-billingdescription: Query Prometheus and Loki billing metrics from Grafana. Use when discussing observability costs, active series, ingestion rates, storage usage, or cardinality analysis.--- # Grafana Billing Metrics Skill Query key billing metrics from Prometheus and Loki through Grafana's data source proxy API. ## Quick Start ```bash # Query both staging and prod (default) uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py # Query specific environment uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --env staging uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --env prod # JSON output for automation uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --json # Filter to specific service uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --service prometheus uv run ${CLAUDE_PLUGIN_ROOT}/skills/grafana-billing/scripts/billing_metrics.py --service loki ``` ## Environment Variables Required - `GRAFANA_STAGING_API_KEY` - API key for staging Grafana workspace - `GRAFANA_PROD_API_KEY` - API key for prod Grafana workspace ## Key Metrics Captured ### Prometheus | Metric | Description | |--------|-------------| | Active Time Series | Current count of active series (billing dimension) | | Samples/sec | Ingestion rate (DPM = samples/sec * 60) | | TSDB Storage | On-disk storage bytes | | Top Cardinality | Top 10 metrics by series count | ### Loki | Metric | Description | |--------|-------------| | Ingestion Rate | GB/day being ingested | | Total Bytes | Cumulative bytes received | | Active Streams | Number of active log streams | | Memory Chunks | Chunks held in memory | ## When to Use Use this skill when the user asks about: - Observability billing or costs - Active time series counts - Prometheus cardinality analysis - Loki ingestion rates - Storage usage for metrics or logs - Comparing staging vs production usage ## Instructions for Claude 1. Run the billing metrics script to gather current data 2. Present the results in a clear, formatted way 3. Highlight any concerning metrics (high cardinality, rapid growth) 4. Compare staging vs prod if both are queried 5. Suggest cost optimization if metrics are unusually high ## Critical Rules - Always check that API keys are set before running - Use `--json` flag when you need to process the output programmatically - Default to querying both environments for comparison - Handle errors gracefully - missing data sources should not crash the script

Frequently asked questions