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.
Borrowing it
Nothing to install: this file belongs to grafana/gcx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/grafana/gcx/main/.claude/skills/integrate-with-gcx/SKILL.mdgit 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/integrate-with-gcx)<a href="https://agentmods.dev/skills/grafana/gcx/integrate-with-gcx"><img src="https://agentmods.dev/badge/skills/grafana/gcx/integrate-with-gcx/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/integrate-with-gcx"><img src="https://agentmods.dev/badge/skills/grafana/gcx/integrate-with-gcx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 187 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- medium Excessive Agency · line 22 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 232 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00219 | $0.03544 |
| Opus 5 | $0.00110 | $0.01772 |
| Sonnet 5 | $0.00044 | $0.00709 |
| Haiku 4.5 | $0.00022 | $0.00354 |
Grade A, and why
integrate-with-gcx 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 12d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate a Capability with gcx
Work autonomously. Inspect the repo, decide, show the decision, keep going. This skill has no approval gates. Ask only when repository evidence genuinely cannot settle something (Asking).
The premise everything follows from: the commands you add are tools other
agents route on. Use/Short/Long/Example, flag help, token cost and
hints are surfaced verbatim through gcx commands and gcx help-tree — that
metadata is an operational contract, not decoration. Names are frozen within a
major version, so the path you pick is the path forever.
| Mode | You are here when |
|---|---|
| Place | where this belongs is undecided |
| Build | placement is known — you decided it, the user stated it, or a sibling skill sent you |
| Review | there is already a branch or PR to get review-ready |
Start with mise run build, then bin/gcx commands >/dev/null && echo ok. Read
AGENTS.md — the entry point for the governing docs; paths cited below are cited
directly, including docs/plans/ and docs/research/, which its map does not
list. Use bin/gcx for your own shell checks (exercise the binary you just
built, not a stale installed one); everything user-facing you author —
Example: fields, help text, docs — says gcx.
Mode: Place
Inventory the tree first — a new leaf competes for every agent's attention:
bin/gcx help-tree
bin/gcx commands --flat -o json
bin/gcx resources list-types
bin/gcx providers list
Settle four things and show them as a short placement section (bullets, not a document):
- Necessity — reuse / extend / consolidate with a sibling / new leaf / not gcx. For a new leaf, name the nearest existing sibling and the one sentence an agent would use to choose between them. If a person who knows the tree can't say which command applies, an agent can't either.
- Path — from
docs/design/command-naming.mdplus precedent in the real tree anddocs/plans/list-subject-verdicts.md. - Backend + wiring — what serves the data, verified by a probe rather than
assumed, and which wiring carries it. A probe that is unavailable, inconclusive
or outside the target you were placed in scope for is reported
UNVERIFIED— never run, and never read as a negative result.gcx apiis a diagnostic fallback, never the integration target. - Readiness — ready / backend prerequisite (named owner) / bounded bootstrap
/ not gcx. Unknowns block by material risk, not by category: an unknown
bearing on API ownership or stability, auth/RBAC, security, mutation safety,
correctness (including an unseen route or payload) or bounded completeness
means backend prerequisite, and for those there is no "ready, pending
verification". Any other unknown is recorded
UNVERIFIEDwith its probe and the work continues. Full list in references/placement-and-readiness.md. Product teams own their API shape, auth, limits and domain data reduction; gcx wraps APIs, it does not fix them.
What ships with it
4 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.
- 12d ago First seen · 280 lines · 219 tokens per session scan A 5e56a6078a78
integrate-with-gcx is a skill published in the GitHub repository grafana/gcx (597 stars, last pushed today), licensed Apache-2.0. It adds 219 tokens to every session and 3,544 once invoked, about $0.0011 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…