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 skills/grafana/agento11y/setup-coding-agentnpx skills add grafana/agento11y --skill setup-coding-agentgit clone --depth 1 https://github.com/grafana/agento11yWhat 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.00121 | $0.06124 |
| Opus 5 | $0.00060 | $0.03062 |
| Sonnet 5 | $0.00024 | $0.01225 |
| Haiku 4.5 | $0.00012 | $0.00612 |
Grade C, and why
setup-coding-agent scanned grade C with 2 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/grafana/agento11y/main/plugins/agento11y/scripts/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/grafana/agento11y/main/plugins/agento11y/scripts/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up a coding agent with Grafana Agent observability
Grafana Agent observability records model calls, tokens, timing, tool names, and
reported or estimated cost. Conversation content is opt-in. The agento11y
binary launches agents and hosts hook-based integrations; pi and OpenCode export
in process. This path installs and configures the integration. It never changes
the user's application code.
Do the steps the machine's current state calls for, not all five. Step 1 says where to start: a machine that needs one credential re-saved does not need a reinstall, and a working setup the user asked a question about needs no changes at all.
Rules
- Never mint, generate, or guess a credential. The token is a Grafana Cloud access-policy token that only the user can create. Ask for it, or tell the user where to click. A made-up token produces a 401.
- Never invent an endpoint URL. The API URL and the OTLP endpoint come from the setup page of the user's own stack (Step 3). Do not assemble one from the stack name; regions differ.
- Never print or echo a token, and never ask for the connection block in
chat. The block the setup page hands out carries a live token, and this
conversation can be exported. The user pastes it into login's own prompt. A
token you have to pass yourself goes in over stdin with
--token-stdin. - Do not edit application code. Adding SDK calls to the user's app is a
different job ("Path B"). If the user wants their own app or agent
instrumented, stop and hand off to the
agento11y-instrumentskill, which ships with thegcxCLI (gcx agent skills install agento11y-instrument). - Do not enable full content capture or guards without asking. The default,
metadata_only, excludes prompts, responses, and tool I/O from generation exports.fullsends that content to Grafana Cloud. Guards send the content they evaluate toAGENTO11Y_ENDPOINTregardless of capture mode. Local mode is separate: it always captures full content in the local store.
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.
- 2d ago First seen · 500 lines · 121 tokens per session scan C 625d406b0f68
setup-coding-agent is a skill published in the GitHub repository grafana/agento11y (95 stars, last pushed 3d ago), licensed Apache-2.0. It adds 121 tokens to every session and 6,124 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.