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 writing-promql-and-logqlgit 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/writing-promql-and-logql)<a href="https://agentmods.dev/skills/consensys/ask-o11y-plugin/writing-promql-and-logql"><img src="https://agentmods.dev/badge/skills/consensys/ask-o11y-plugin/writing-promql-and-logql/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/writing-promql-and-logql"><img src="https://agentmods.dev/badge/skills/consensys/ask-o11y-plugin/writing-promql-and-logql.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.00057 | $0.00257 |
| Opus 5 | $0.00028 | $0.00129 |
| Sonnet 5 | $0.00011 | $0.00051 |
| Haiku 4.5 | $0.00006 | $0.00026 |
Grade A, and why
writing-promql-and-logql 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 3d 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.
What it actually says
PromQL
- Use
rate()for counters, never raw counter values - Aggregate before
rate()for efficiency - Use label matchers to reduce cardinality
- Start with short time ranges, expand if needed
See references/promql.md for the full guide — counter, gauge, and histogram patterns, aggregation pitfalls, and worked examples.
LogQL
- Start with label filters, add line filters second
- Use JSON parsing only when needed
See references/logql.md for the full guide, including the label-discovery workflow for unfamiliar clusters.
Choosing signal
Prefer the cheapest signal that answers the question: metrics for trends and aggregates, logs for events and errors, traces for request-level latency and causality. Do not query all three when one answers the question directly.
What ships with it
2 files 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.
- 3d ago First seen · 31 lines · 57 tokens per session scan A fdd26ae559d7
writing-promql-and-logql is a skill published in the GitHub repository Consensys/ask-o11y-plugin (42 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 257 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-09-07.
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…