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 voidhashcom/lensflare --skill analyze-tracegit clone --depth 1 https://github.com/voidhashcom/lensflareWrote 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/voidhashcom/lensflare/analyze-trace)<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.
<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>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.00063 | $0.00337 |
| Opus 5.5 | $0.00025 | $0.00135 |
| Sonnet 5.5 | $0.00013 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
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.
What it actually says
Analyze a trace in Lensflare
- If the user supplied a
traceId, use it. Otherwise calllensflare:queryTelemetryto find a relevant trace (filter byserviceName, time, or attributes). Pick the trace whose root span has the highestdurationUsor whosestatus = "error". - Call
lensflare:getTracewith the resolveddatasetIdandtraceId. If it returnsnull, double-check thetraceIdwithqueryTelemetry(traceId = "<id>") before reporting back. - Read
summary.spanCountandsummary.erroredSpanCount. If errors exist, lead with them: name + service +durationUs. - Walk
spansin order. Highlight the longest span, the deepest chain, and any span whosestatus = "error"or whose duration is more than 50% of its parent's. - Surface
relatedEventsonly when they materially explain a failure (e.g. an exception event on the failing span). - 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\"".
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.
- 2mo ago First seen · 14 lines · 63 tokens per session scan A 622ac5badf7b
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.
analyze-trace compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| analyze-tracevoidhashcom/lensflare | Skill | 100 | 4mo ago | MIT | A | 63 | Claude Code |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | yesterday | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | 3d ago | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 319 | yesterday | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 1.9k | 23d ago | MIT | A | 36 | Claude Code |
| triaging-web-analytics-supportPostHog/posthog | Skill | 41k | yesterday | none | A | 151 | Claude Code, Codex |