gcx is a command-line tool that lets people and AI coding agents manage and inspect Grafana Cloud, Enterprise, and open-source instances. It provides access to dashboards, alerts, SLOs, metrics, logs, and traces, with workflows for alert investigation, dashboard management, GitOps, and observability setup. Its catalogue entries provide agent instructions and extensions for using gcx.
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 grafana/gcx --skill slo-check-statusgit clone --depth 1 https://github.com/grafana/gcxWrote 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/grafana/gcx/slo-check-status)<a href="https://agentmods.dev/skills/grafana/gcx/slo-check-status"><img src="https://agentmods.dev/badge/skills/grafana/gcx/slo-check-status/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/grafana/gcx/slo-check-status"><img src="https://agentmods.dev/badge/skills/grafana/gcx/slo-check-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00131 | $0.01433 |
| Opus 5 | $0.00066 | $0.00717 |
| Sonnet 5 | $0.00026 | $0.00287 |
| Haiku 4.5 | $0.00013 | $0.00143 |
Grade A, and why
slo-check-status 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 11d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLO Status Checker
Check SLO health, budget consumption, and trends. Route to investigation or optimization as needed.
Core Principles
- Use
gcxcommands — do not call Grafana APIs directly - Trust the user's expertise — no hand-holding or excessive explanation
- Use
-o jsonfor agent processing, default format for user display - Show graphs for time-series data (timeline commands default to graph output)
Workflow
Step 1: Overview or Specific SLO
If the user asks about all SLOs (no specific UUID):
gcx slo definitions list
This shows UUID, name, target objective, window, and status for all SLOs.
Then get the health summary:
gcx slo definitions status
This shows SLI, error budget, and health status for all SLOs in a table.
If the user asks about a specific SLO (UUID or name provided):
gcx slo definitions status <UUID> -o wide
The -o wide output includes additional columns: BURN_RATE, SLI_1H, and SLI_1D, which give a richer picture of recent performance.
Step 2: Interpret Status Values
| Status | Meaning |
|---|---|
| OK | SLI >= objective. SLO is healthy. |
| BREACHING | SLI < objective. Error budget is being consumed. |
| NODATA | No Prometheus metrics from recording rules. |
| Creating | SLO provisioning in progress. |
| Updating | SLO update in progress. |
| Deleting | SLO deletion in progress. |
| Error | SLO in error state — check the SLO configuration. |
NODATA handling: Recording rule metrics may not be available if the destination datasource is misconfigured or recording rules are not evaluating. Note this to the user and suggest checking the destination datasource configuration.
Step 3: Timeline (Conditional)
Show the timeline when:
- The user asks about trends or historical data
- Any SLO shows BREACHING status
All SLOs timeline:
gcx slo definitions timeline --from now-7d --to now
Specific SLO timeline:
gcx slo definitions timeline <UUID> --from now-7d --to now
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.
- 11d ago First seen · 156 lines · 131 tokens per session scan A e775c8115d08
slo-check-status is a skill published in the GitHub repository grafana/gcx (597 stars, last pushed today), licensed Apache-2.0. It adds 131 tokens to every session and 1,433 once invoked, about $0.0007 per session on Opus 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-08-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…