analyze-trace

analyze-trace is a skill for Claude Code from voidhashcom/lensflare. It costs 63 tokens per session (337 once invoked), scanned A, original, MIT.

A procedure for examining a Lensflare trace one span at a time. A trace follows one software request, while spans represent the individual operations inside it and their parent-child relationships.

In plain words
What is it for?
Use it for trace-based performance investigations, production or development request post-mortems, and follow-up queries for related failures.
Why use it?
It helps explain slow requests and failures by showing which operation took the most time, where errors occurred, and how the operations were connected.

Skill for Claude Code

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

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

Good fit Use it for trace-based performance investigations, production or development request post-mortems, and follow-up queries for related failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/voidhashcom/lensflare/analyze-trace
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 analyze-trace
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 analyze-trace

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/voidhashcom/lensflare/analyze-trace"><img src="https://agentmods.dev/badge/skills/voidhashcom/lensflare/analyze-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 337 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.00063 $0.00337
Opus 5.5 $0.00025 $0.00135
Sonnet 5.5 $0.00013 $0.00067
Haiku 4.5 $0.00006 $0.00034

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

Security

Grade A, and why

analyze-trace 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/analyze-trace/SKILL.md · 14 lines

What it actually says

Analyze a trace in Lensflare

  1. If the user supplied a traceId, use it. Otherwise call lensflare:queryTelemetry to find a relevant trace (filter by serviceName, time, or attributes). Pick the trace whose root span has the highest durationUs or whose status = "error".
  2. Call lensflare:getTrace with the resolved datasetId and traceId. If it returns null, double-check the traceId with queryTelemetry (traceId = "<id>") before reporting back.
  3. Read summary.spanCount and summary.erroredSpanCount. If errors exist, lead with them: name + service + durationUs.
  4. Walk spans in order. Highlight the longest span, the deepest chain, and any span whose status = "error" or whose duration is more than 50% of its parent's.
  5. Surface relatedEvents only when they materially explain a failure (e.g. an exception event on the failing span).
  6. End with a one-line root-cause hypothesis and a suggested follow-up query. Example: "to see all requests with this error: attributes.http.status_code = 500 and serviceName = \"api\"".
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 · 14 lines · 63 tokens per session scan A 622ac5badf7b

Subscribe to this mod's changes

analyze-trace is a skill published in the GitHub repository voidhashcom/lensflare (100 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 337 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-08-30.

Related

analyze-trace compared with skills from other repositories

analyze-trace next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
analyze-tracevoidhashcom/lensflareSkill1004mo agoMITA63Claude 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