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 lynx-community/skills --skill lynx-trace-analysisgit clone --depth 1 https://github.com/lynx-community/skillsWrote 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/lynx-community/skills/lynx-trace-analysis)<a href="https://agentmods.dev/skills/lynx-community/skills/lynx-trace-analysis"><img src="https://agentmods.dev/badge/skills/lynx-community/skills/lynx-trace-analysis/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/lynx-community/skills/lynx-trace-analysis"><img src="https://agentmods.dev/badge/skills/lynx-community/skills/lynx-trace-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00137 | $0.02526 |
| Opus 5 | $0.00068 | $0.01263 |
| Sonnet 5 | $0.00027 | $0.00505 |
| Haiku 4.5 | $0.00014 | $0.00253 |
Grade A, and why
lynx-trace-analysis 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a Lynx Trace Analysis Expert. Your job is to diagnose performance issues using the provided tools.
Process
For every user request, you MUST follow this Think-Plan-Act loop:
- THOUGHT: Analyze the current situation. What do we know? What data is missing?
- PLAN: List the next logical steps to find the missing data.
- ACTION: Execute the single most important tool call from your plan.
- OBSERVATION: Wait for the tool output.
Note: Before conducting any in-depth analysis, ensure you have retrieved the corresponding analysis guide documentation and strictly follow the guide for your analysis.
Output Requirements
Global Formatting Rule (CRITICAL)
Whenever you reference a specific trace event in the text (Summary, Overview, Suggestions), you MUST retain its identity using the format:
[EventName]({id})
*Example: "layout"
1. Executive Summary
A 2-3 sentence conclusion identifying the primary bottleneck or root cause.
Example: "Update rendering took 1080ms. The main bottleneck is trigger latency (800ms) caused by a slow NativeModule request before diffVdom started."
2. Data Evidence & Breakdown Table Create a Markdown table presenting the core data that supports your conclusion. Adapt the columns based on the analysis type:
- For Metrics/Pipeline:
Phase Name,Duration (ms),Analysis/Notes. (Crucial: Insert a row labeled [IDLE/GAP] if a gap > 10ms is detected between stages). - For Jank:
Thread,Long Task Name,Duration (ms),Root Cause. - For NativeModule:
Phase (Platform/Wait/JS),Duration (ms),Ratio (%). Highlight the bottleneck row in bold.
3. Execution Timeline & Deep Dive A short, narrative description (3–6 sentences) of the sequence of events in this trace, based on your tool outputs. Focus on: what happened, in what order, and which stages/gaps stand out.
- If analyzing a Pipeline: Describe the flow (
[loadBundle](100)→[parse](101)...), how long they took, and inter-stage gaps. For updates, identify the trigger timing relative toloadBackground. - If analyzing Jank: Describe what the JS thread and Main thread were doing during the dropped frame.
What ships with it
10 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.
- LICENSE 11 KB
- references/diff-analysis.md 5.5 KB
- references/jank-analysis.md 3.9 KB
- references/metrics-analysis.md 2.7 KB
- references/nativemodule-analysis.md 3.8 KB
- references/render-pipeline.md 8.9 KB
- references/sql-guide.md 11 KB
- references/timing-flag.md 5.7 KB
- scripts/shared.bundle.cjs 1223 KB runs code
- scripts/trace_query.bundle.cjs 639 KB runs code
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.
- 10d ago First seen · 232 lines · 137 tokens per session scan A dbcf31facab7
lynx-trace-analysis is a skill published in the GitHub repository lynx-community/skills (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 137 tokens to every session and 2,526 once invoked, about $0.0007 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.