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 Consensys/ask-o11y-plugin --skill building-dashboardsgit clone --depth 1 https://github.com/Consensys/ask-o11y-pluginWrote 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/consensys/ask-o11y-plugin/building-dashboards)<a href="https://agentmods.dev/skills/consensys/ask-o11y-plugin/building-dashboards"><img src="https://agentmods.dev/badge/skills/consensys/ask-o11y-plugin/building-dashboards/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/consensys/ask-o11y-plugin/building-dashboards"><img src="https://agentmods.dev/badge/skills/consensys/ask-o11y-plugin/building-dashboards.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.00081 | $0.00701 |
| Opus 5.5 | $0.00032 | $0.00280 |
| Sonnet 5.5 | $0.00016 | $0.00140 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
building-dashboards 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 1mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard creation workflow
Always create dashboards step by step — never generate a single large dashboard JSON with many panels in one call. Large payloads often exceed size limits and fail silently.
- First: Create an empty dashboard (minimal JSON: title, optional folder UID, empty or minimal
panelsarray). - Then: Add panels iteratively — use the update dashboard tool to add one or a few panels at a time (e.g., add a row or 1–2 panels per call).
- If the user wants many panels: Create the shell, then add panels in small batches until the dashboard is complete.
This keeps each tool call payload small and reliable.
Panel queries — Prefer label matchers and aggregation in PromQL so panels stay fast; set sensible time ranges per panel. When unsure which metric names exist, run the metric-name listing tool with a targeted regex before writing panel queries.
Panel type selection
| Data shape | Panel type |
|---|---|
| Metric over time | timeseries |
| Single value (+ trend) | stat |
| Value against min/max | gauge |
| Comparison across items | barchart / bar gauge |
| Multi-column rows | table |
| Distribution over time | heatmap |
| Histogram of one window | histogram |
| Part of a whole | piechart |
| Log streams | logs |
| Trace results | traces |
Panel JSON essentials
gridPosis a 24-column grid (full=24, half=12, third=8) with height ≈ 30px per unit- Set
fieldConfig.defaults.unit(reqps,percentunit,bytes,ms,short) or numbers render raw - Thresholds: green/yellow/red
stepswith the first step atvalue: null legendFormatnames series readably; substitute label values with${__field.labels.instance}-style placeholders- Template variables:
{ "name":"job", "type":"query", "query":{"query":"label_values(up, job)"}, "refresh":2, "includeAll":true, "multi":true }— chained variables refine the next dropdown
See references/dashboard-json.md for the full schema — panel JSON, units table, variables, transformations (e.g. an "Error %" calculateField), data links, and deploy annotations.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +33 lines · +46 tokens per session a55e93089586
- 1mo ago First seen · 22 lines · 35 tokens per session scan A 186bd3352d46
building-dashboards is a skill published in the GitHub repository Consensys/ask-o11y-plugin (42 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 701 once invoked, about $0.0003 per session on Opus 5.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-09-07.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.