agentmods.dev

query-logs

query-logs is a skill for Claude Code from voidhashcom/lensflare. It costs 53 tokens per session (354 once invoked), scanned A, original, MIT.

A tool that turns a plain-language question about logs or telemetry into a structured Lensflare query and returns matching records. Telemetry is operational data such as log messages, errors, statuses, and request times.

In plain words
What is it for?
Use it to find errors, slow requests, messages containing specific text, or records with a particular HTTP status, then review counts, time ranges, and examples.
Why use it?
It lets developers search monitoring data without writing the query language by hand, while using structured fields to reduce irrelevant results.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the lensflare-desktop plugin — 3 skills shipped together

not rated 100repo 4mo ago A scan 53 tokens original MIT

Good fit Use it to find errors, slow requests, messages containing specific text, or records with a particular HTTP status, then review counts, time ranges, and examples.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/voidhashcom/lensflare/query-logs
View source ↗ voidhashcom/lensflare lensflare.vercel.app
Install

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.

Any agent
npx skills add voidhashcom/lensflare --skill query-logs
Clone the repo
git clone --depth 1 https://github.com/voidhashcom/lensflare

Made for: Claude Code.

Or install lensflare-desktop, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

agentmods badge for query-logs

README.md
[![agentmods](https://agentmods.dev/badge/skills/voidhashcom/lensflare/query-logs/github.svg)](https://agentmods.dev/skills/voidhashcom/lensflare/query-logs)
Your own site
<a href="https://agentmods.dev/skills/voidhashcom/lensflare/query-logs"><img src="https://agentmods.dev/badge/skills/voidhashcom/lensflare/query-logs/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.

agentmods 80×15 button for query-logs

Your own site · 80×15
<a href="https://agentmods.dev/skills/voidhashcom/lensflare/query-logs"><img src="https://agentmods.dev/badge/skills/voidhashcom/lensflare/query-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 354 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.00354
Opus 5.5 $0.00021 $0.00142
Sonnet 5.5 $0.00011 $0.00071
Haiku 4.5 $0.00005 $0.00035

Measured 2mo ago against content hash b579b689b702, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

query-logs 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 2mo 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.

plugins/lensflare-desktop/skills/query-logs/SKILL.md · 24 lines

What it actually says

Query Lensflare telemetry

You have access to a structured query language exposed via lensflare:queryTelemetry. The full grammar is in that tool's description — read it. Examples:

  • "errors from the api service" → serviceName = "api" and (level in ["error", "fatal"] or status = "error")
  • "slow requests" → durationUs >= 1000000
  • "anything that mentions ECONNRESET" → message ~= /ECONNRESET/
  • "logs with http status 500" → attributes.http.status_code = 500

Steps:

  1. Identify the dataset. Use lensflare:listDatasets if needed.
  2. Translate the user's prose into a single query string. Prefer structured comparisons over free-text — fewer false positives, easier to refine.
  3. Call lensflare:queryTelemetry with limit: 50 (or as requested). Use cursor from usage.nextPageCursor if the user asks for more.
  4. Summarise the page: counts, time range covered, dominant serviceName / level. Show a few example records inline (id, level, message or name, timestamp).
  5. Offer a refined query if the result set is too broad or too narrow.

Never invent fields — call queryTelemetry with no query first if you're unsure; the records show you the available shape.

Changes

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.

  1. 2mo ago First seen · 24 lines · 53 tokens per session scan A b579b689b702

Subscribe to this mod's changes

query-logs is a skill published in the GitHub repository voidhashcom/lensflare (100 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 354 once invoked, about $0.0002 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-08-30.

Analytics and metricsDebugging
Related

query-logs compared with skills from other repositories

query-logs next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
query-logsvoidhashcom/lensflareSkill1004mo agoMITA53Claude Code
systematic-debuggingopen-metadata/OpenMetadataSkill16kyesterdayApache-2.0A37Claude Code
log-error-digestzebbern/claude-code-guideSkill4.7k3d agoMITA71Claude Code, Codex
cwv-optimizeradobe/skillsSkill319yesterdayApache-2.0A112Claude Code
ci-fixersipyourdrink-ltd/bernsteinSkill1.2kyesterdayApache-2.0A15Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skillsSkill1.9k23d agoMITA36Claude Code
triaging-web-analytics-supportPostHog/posthogSkill41kyesterdaynoneA151Claude Code, Codex