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 agentmods add instructions/grafana/gcx/agents-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/instructions/grafana/gcx/agents-md)<a href="https://agentmods.dev/instructions/grafana/gcx/agents-md"><img src="https://agentmods.dev/badge/instructions/grafana/gcx/agents-md.svg" alt="Measured on agentmods" 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 | $0.03282 | $0.03282 |
| Opus 5 | $0.01641 | $0.01641 |
| Sonnet 5 | $0.00656 | $0.00656 |
| Haiku 4.5 | $0.00328 | $0.00328 |
Grade A, and why
gcx AGENTS.md 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 4d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gcx — Agent & Developer Entry Point
Lightweight map for autonomous coding agents. Read this first, then navigate to specific docs on demand.
Quick Start
gcx is a unified CLI for managing Grafana resources. It operates in two tiers: (1) a K8s resource tier that uses Grafana 12+'s Kubernetes-compatible API via k8s.io/client-go for dashboards, folders, and other K8s-native resources, and (2) a Cloud provider tier with pluggable providers for Grafana Cloud products (SLO, Synthetic Monitoring, IRM, Fleet Management, etc.) that use product-specific REST APIs. Built in Go, it uses Cobra for CLI structure.
Documentation Map
| File | Purpose |
|---|---|
| VISION.md | Goals, product surface, roadmap themes, release timeline |
| CONSTITUTION.md | Invariants — things that cannot change without explicit human approval |
| ARCHITECTURE.md | System overview (all 7 subsystems), pipeline diagrams, ADR index |
| DESIGN.md | CLI UX design: command grammar, output model, exit codes |
| CONTRIBUTING.md | Dev setup, testing environment, contribution workflow |
| docs/architecture/ | Deep-dive architecture docs (patterns, resource model, CLI layer, data flows, …) |
| docs/design/ | Prescriptive UX implementation rules (output, errors, agent mode, naming, …) |
| docs/reference/ | Provider guides, CLI reference, migration analysis |
| docs/_templates/ | Spec and planning templates (feature, bugfix, refactor, ADR, research) |
Architecture at a Glance
Two tiers: K8s resource tier (dashboards, folders via /apis) and Cloud provider tier (SLO, SM, IRM, etc. via product REST APIs). See ARCHITECTURE.md for pipeline diagrams and extension pipelines.
Key Conventions
Authoritative source: CONSTITUTION.md (invariants) and DESIGN.md (UX rules). This is the quick-reference summary.
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.
- 4d ago First seen · 187 lines · 3,282 tokens per session scan A e86d676b24e5
gcx AGENTS.md is an instructions file published in the GitHub repository grafana/gcx (584 stars, last pushed today), licensed Apache-2.0. It adds 3,282 tokens to every session, about $0.0164 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.