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 setup-local-guardsgit 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/setup-local-guards)<a href="https://agentmods.dev/skills/grafana/agento11y/setup-local-guards"><img src="https://agentmods.dev/badge/skills/grafana/agento11y/setup-local-guards/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/setup-local-guards"><img src="https://agentmods.dev/badge/skills/grafana/agento11y/setup-local-guards.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00073 | $0.02182 |
| Opus 5.5 | $0.00029 | $0.00873 |
| Sonnet 5.5 | $0.00015 | $0.00436 |
| Haiku 4.5 | $0.00007 | $0.00218 |
Grade C, and why
setup-local-guards scanned grade C with 1 finding 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 24d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
agento11y guards test 'rm -rf /tmp/agento11y-guard-example' How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up local guard packs
Inspect the installed configuration, explain the relevant packs, ask for approval, then configure and test only the user's choices. For a question about existing behavior, stop after explaining it; do not change settings.
Safety rules
- Ask before enabling or disabling guards, changing packs, editing rules, or changing the session destination.
- Preserve custom rules, credentials, capture settings, and the user's Cloud forwarding choice.
- Never execute a dangerous command to test a guard. Pass quoted command text only to
agento11y guards test. - Never test with real secrets or print
config.env; it can contain credentials. - Explain that guards cover only tool calls submitted through the integration. They are not an operating-system sandbox.
- Do not claim live protection from an offline dry run. A matching rule and a working host hook are separate checks.
1. Inspect the installation
Run:
agento11y --version
agento11y guards test --help
agento11y local status
If the binary or local guard commands are missing, explain what is missing.
Offer agento11y skills show setup-coding-agent for installation or host integration setup.
Do not assume an older binary includes this skill or every pack.
Local mode requires macOS or Linux.
Identify the target coding agent, its installed agento11y integration, and whether its sessions use the local daemon or go directly to Cloud.
Opening the local app does not route a running agent through it.
For Codex, ask the user to open /hooks and trust the agento11y hooks after installation.
Use the running app's Security > Guards to inspect the saved enablement, rules path, pack selections, and compilation errors.
If the app is stopped, ask before running agento11y local open to start it.
Use the displayed rules path rather than assuming ~/.config/agento11y/guards.toml.
Read an existing rules file before proposing edits; do not replace it with a template.
Use agento11y doctor --json if installation or routing needs further diagnosis.
Explain that doctor probes configured endpoints and obtain approval before those requests.
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.
- 24d ago Changed ec59514ce76f
- 27d ago Changed · +2 lines a3e15e4368bb
- 28d ago First seen · 172 lines · 73 tokens per session scan C cd8c8f6e7947
setup-local-guards is a skill published in the GitHub repository grafana/agento11y (129 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 2,182 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-18.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…