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 skills add grafana/agento11y --skill agento11y-experimentsgit 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/skills/grafana/agento11y/agento11y-experiments)<a href="https://agentmods.dev/skills/grafana/agento11y/agento11y-experiments"><img src="https://agentmods.dev/badge/skills/grafana/agento11y/agento11y-experiments/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/agento11y/agento11y-experiments"><img src="https://agentmods.dev/badge/skills/grafana/agento11y/agento11y-experiments.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.00067 | $0.01811 |
| Opus 5 | $0.00034 | $0.00905 |
| Sonnet 5 | $0.00013 | $0.00362 |
| Haiku 4.5 | $0.00007 | $0.00181 |
Grade A, and why
agento11y-experiments 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 10d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Observability experiments
Use this skill when adding framework-free offline evaluation to a Python project.
The public SDK surface is agento11y.experiments; do not use removed v0 runner
APIs.
This is the reference for the run-side API. If you don't yet know which evaluators
you need or have no test cases, start with the agento11y-eval-starter skill — it reads
your agent, recommends evaluators, writes a starter suite, and generates a minimal
runner; come here for the deeper patterns (binding existing generations, auditable
LLM judges, cross-process verifiers, pass@k/pass^k).
The normal setup cost for an already instrumented agent should be small:
- Import
experimentsfromagento11y. - Define a
TestSuitewithTestCases. - Wrap the existing agent call in
with exp.trial(case) as trial:. - Bind the generation/conversation ids your normal instrumentation already
produced, or call
trial.record_io(...)when the harness owns the call. - Emit one final score and any supporting scores.
Setup
pip install "agento11y>=0.11.0"
Required environment:
export AGENTO11Y_ENDPOINT=https://agento11y-prod-<region>.grafana.net
export AGENTO11Y_AUTH_TOKEN=<grafana-cloud-ingestion-api-key>
# Optional when the endpoint requires tenant-scoped basic auth.
export AGENTO11Y_AUTH_TENANT_ID=<stack-id>
# Optional UI host for deep links when it differs from AGENTO11Y_ENDPOINT.
export AGENTO11Y_GRAFANA_URL=https://<your-stack>.grafana.net
Local-suite experiment ingest uses only the Cloud ingestion API key. Stored
suite push/pull additionally uses AGENTO11Y_CONTROL_ENDPOINT and a Grafana
service-account token in AGENTO11Y_SERVICE_ACCOUNT_TOKEN.
Experimental OTel eval spans/events are disabled by default. Opt in only when asked:
with experiments.experiment("nightly", use_experimental_otel=True) as exp:
...
Recommended Pattern
from agento11y import experiments
suite = experiments.TestSuite(
suite_id="smoke",
name="Smoke",
version="2026-06-29",
test_cases=[
experiments.TestCase(test_case_id="capital-fr", input="Capital of France?", expected="Paris"),
],
)
verifier = experiments.Evaluator(evaluator_id="exact_match", version="2026-06-29", kind="deterministic")
with experiments.experiment(
"PR experiment",
experiment_id=f"pr-{git_sha}",
suite=suite,
planned_trial_count=len(suite.test_cases),
candidate={"git_sha": git_sha, "model_name": "gpt-4o-mini"},
tags=["ci"],
) as exp:
for case in suite.test_cases:
with exp.trial(case) as trial:
answer = call_your_agent(case.input)
# If normal instrumentation already created a conversation/generation,
# bind those ids instead of recording duplicate I/O.
# trial.bind_conversation(conversation_id)
# trial.bind_generation(generation_id, conversation_id=conversation_id)
trial.record_io(
input=case.input,
output=answer,
model_provider="openai",
model_name="gpt-4o-mini",
)
passed = str(case.expected).lower() in answer.lower()
trial.final_score(
1.0 if passed else 0.0,
passed=passed,
explanation=f"expected {case.expected!r}, got {answer!r}",
evaluator=verifier,
)
print(exp.url)
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.
- 10d ago First seen · 222 lines · 67 tokens per session scan A b8508b968e94
agento11y-experiments is a skill published in the GitHub repository grafana/agento11y (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 1,811 once invoked, about $0.0003 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…