Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add alivirgo/Major-AI-Skills --skill grafanagit clone --depth 1 https://github.com/alivirgo/Major-AI-SkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/alivirgo/major-ai-skills/grafana)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/grafana"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/grafana/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/grafana"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/grafana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.01348 |
| Opus 5.5 | $0.00015 | $0.00539 |
| Sonnet 5.5 | $0.00007 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
grafana scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 21d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grafana Dashboards & Alerts AI Skill Guide (Claude)
Overview & Engine Architecture
Grafana visualizes telemetry from data sources (Prometheus, Loki, Tempo, CloudWatch, …) via dashboards (panels + variables) and unified alerting (multi-source rules → contact points). Agents design on-call-first layouts (RED at top), provision JSON/YAML in Git, and keep alert expressions identical to @prometheus rule sources of truth.
┌─────────────────────────────────────────────────────────────┐
│ Grafana operational stack │
│ │
│ Data sources (Prometheus/Loki/…) │
│ ↓ queries (PromQL/LogQL) │
│ Dashboards (variables, rows, panels) │
│ Unified alerting → contact points → Slack/PagerDuty │
│ Provisioning: datasources.yaml + dashboards/*.json │
└─────────────────────────────────────────────────────────────┘
When to use / when not to
Use when
- Building service SLO dashboards, infra overviews, or migration from click-ops UI to Git.
- Wiring datasource UIDs, folder RBAC, and alert routes with runbooks.
- Debugging “no data”, variable cascades, or alert notification storms.
Do not use when
- Defining canonical alert rules without Prometheus—prefer recording/alert rules in Prometheus when already used; Grafana alerts duplicate logic if unmanaged.
- SSO/LDAP enterprise auth design (deployment-specific pointers only).
Operational Capabilities & Agent Directives
- One dashboard = one operational question (on-call service view vs capacity planning).
- Variables:
env,namespace,servicevialabel_values; never hardcode prod names in panel queries. - Top row RED: request rate, error ratio, latency percentiles from recording rules when available.
- Limit series per panel; use aggregations (
sum by (status))—no 500-line legends. - Provision critical dashboards under
grafana/provisioning/dashboards/; review in PRs like code. - Alerts: severity label,
runbook_urlannotation, mute windows documented; test contact point in staging. - Datasource UIDs stable in JSON—random UID breaks provisioning across envs; set explicitly.
- Explore for ad-hoc debug; durable knowledge lives in dashboards/runbooks, not screenshots.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 21d ago Changed · +69 lines · +14 tokens per session 9ee1caba690f
- 1mo ago Changed · -5 tokens per session b3623cd3cb51
- 1mo ago First seen · 81 lines · 28 tokens per session scan A 01e953493c39
grafana is a skill published in the GitHub repository alivirgo/Major-AI-Skills (2 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,348 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
monitoring-setup
Set up comprehensive monitoring with Prometheus, Grafana, and alerting. Covers metrics, dashboards, SLOs, and on-call runbooks.
Observability with Prometheus & Grafana
Production-grade observability stack with Prometheus metrics, Grafana dashboards, PromQL query language, alerting rules, and AI-powered anomaly detection for modern cloud-native applications.
querying-yandex-cloud
Read Yandex Cloud through its REST API. Applies to any question about VMs, metrics, logs, audit events, Kubernetes, managed databases, serverless, networking or any other Yandex Cloud resource. Never shell out to the yc CLI — it is not how this agent reaches Yandex Cloud and is usually not installed.
grafana-expert
Expert-level Grafana dashboards, visualization, data sources, alerting, and production operations. Use when the user mentions dashboards, visualization, monitoring, observability, or alerting, or when the task involves Grafana Architecture, Installation on Kubernetes, Data Sources, or Dashboard JSON.
monitoring-expert
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.
k8s-monitoring-alerting
A Kubernetes diagnostic and repair method for Prometheus and Grafana monitoring problems, including alerts that do not trigger. Prometheus collects measurements, while Grafana displays them in dashboards.