Grafana Agent Observability is an SDK and plugin collection that collects telemetry from coding agents and AI agents built into applications, including sessions, tool calls, traces, tokens, costs, generations, and evaluations. Developers use it to monitor coding-agent usage or instrument agents in their own services, with SDKs for several programming languages. The catalogue add-ons help configure and use this observability workflow with coding agents.
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/agento11y/agents-mdgit clone --depth 1 https://github.com/grafana/agento11yWrote 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/agento11y/agents-md)<a href="https://agentmods.dev/instructions/grafana/agento11y/agents-md"><img src="https://agentmods.dev/badge/instructions/grafana/agento11y/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.02571 | $0.02571 |
| Opus 5 | $0.01286 | $0.01286 |
| Sonnet 5 | $0.00514 | $0.00514 |
| Haiku 4.5 | $0.00257 | $0.00257 |
Grade A, and why
agento11y 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on agento11y
This file is for agents working on this repo (the SDKs in go/, python/, js/, java/, dotnet/ and the launchers in plugins/).
For agents working in a consumer project (instrumenting their app, or installing one of our plugins), point them at llms.txt instead. That is the file we ship to users.
Read the README and mise tasks for the obvious stuff: layout, package names, where languages live. This file only documents what you can't discover by looking.
Git blame ignores the local viewer reformat in .git-blame-ignore-revs. Run git config blame.ignoreRevsFile .git-blame-ignore-revs once in each clone.
Proto is the source of truth
proto/agento11y/v1/*.proto is the source of truth. Generated stubs live under each language tree:
- Go:
go/proto/agento11y/ - Python:
python/agento11y/internal/gen/agento11y/ - JS:
js/proto/agento11y/(the runtime loads.protofiles directly, no codegen) - Java, .NET: compiled on build via the gradle protobuf plugin and
Grpc.Tools; no committed stubs.
Never edit generated files. Edit the .proto, then:
mise run generate:proto
CI runs mise run check:proto and fails the build if the committed stubs drift from the proto. Tool versions are pinned in mise.toml so output is byte-identical across machines. See docs/development.md for the full table.
Secret patterns are the second source of truth
redaction/patterns.json is the only editable secret-pattern table. Each engine gets its list generated from it, next to hand-written code: go/agento11y/redaction_patterns_gen.go, python/agento11y/_redaction_patterns.py, js/src/redaction-patterns.generated.ts, dotnet/src/Grafana.Agento11y/RedactionPatterns.g.cs, plugins/agento11y/internal/redact/patterns_gen.go.
Never edit those five files. Edit patterns.json, then:
mise run generate:redaction
CI runs mise run check:redaction in the same job as the proto drift check. redaction/README.md covers the pattern fields and the shared fixtures.
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.
- 5d ago First seen · 112 lines · 2,571 tokens per session scan A ad0b4985483c
agento11y AGENTS.md is an instructions file published in the GitHub repository grafana/agento11y (99 stars, last pushed today), licensed Apache-2.0. It adds 2,571 tokens to every session, about $0.0129 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.
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).