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 agentmods add skills/voidhashcom/lensflare/query-logsnpx skills add voidhashcom/lensflare --skill query-logsgit clone --depth 1 https://github.com/voidhashcom/lensflareWhat 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 | $0.00053 | $0.00354 |
| Opus 5 | $0.00026 | $0.00177 |
| Sonnet 5 | $0.00011 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
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 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
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:
- Identify the dataset. Use
lensflare:listDatasetsif needed. - Translate the user's prose into a single query string. Prefer structured comparisons over free-text — fewer false positives, easier to refine.
- Call
lensflare:queryTelemetrywithlimit: 50(or as requested). Usecursorfromusage.nextPageCursorif the user asks for more. - Summarise the page: counts, time range covered, dominant
serviceName/level. Show a few example records inline (id, level, message or name, timestamp). - 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.
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 · 24 lines · 53 tokens per session scan A b579b689b702
query-logs is a skill published in the GitHub repository voidhashcom/lensflare (98 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 354 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…