SkillsAdd

nodnarbnitram/claude-code-extensions

grafana-billing

Query Prometheus and Loki billing metrics from Grafana. Use when discussing observability costs, active series, ingestion rates, storage usage, or cardinality analysis.

First seen Jan 24, 2026

Installation

$ npx skills add nodnarbnitram/claude-code-extensions --skill grafana-billing
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

grafana-dashboards Similar name
wshobson/agents 11.6K installs
grafana-oss Similar name
grafana/skills

Configure Grafana OSS — provisions dashboards from YAML, sets up data sources (Prometheus / Lok…

3.9K installs
grafana-scenes Similar name
grafana/skills

Build Grafana plugin pages using the @grafana/scenes framework. Use when creating new scene pag…

2.8K installs
grafana-dashboard Similar name
aj-geddes/useful-ai-prompts

Create professional Grafana dashboards with visualizations, templating, and alerts. Use when bu…

482 installs
prometheus-grafana Similar name
bagelhole/devops-security-agent-skills

Set up metrics collection and visualization with Prometheus and Grafana. Configure scrape targe…

320 installs
grafana-dashboards Similar name
sickn33/agentic-awesome-skills

Create and manage production-ready Grafana dashboards for comprehensive system observability.

311 installs

Also in this package

Other skills from nodnarbnitram/claude-code-extensions · top by installs.

npx skills add nodnarbnitram/claude-code-extensions
tauri-v2 7.2K code-reviewer 291 ha-voice 218 esphome-config-helper 133 frigate-configurator 109 ha-energy 102 ha-automation 89 kubernetes-operations 84 kubernetes-health 83 ha-api 83

Browse all from nodnarbnitram/claude-code-extensions

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 16
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,519 B
  • docs SUMMARY.md 191 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 67 installs

SKILL.md

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/skills/grafana-billing/scripts/billing_metrics.py

# Query specific environment
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --env staging
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --env prod

# JSON output for automation
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --json

# Filter to specific service
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --service prometheus
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --service loki

Environment Variables Required

  • GRAFANASTAGINGAPI_KEY - API key for staging Grafana workspace
  • GRAFANAPRODAPI_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