Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add zystem-io/zymtrace-skills/plugin install zymtraceWrote 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/zystem-io/zymtrace-skills/troubleshoot-zymtrace-profiler)<a href="https://agentmods.dev/skills/zystem-io/zymtrace-skills/troubleshoot-zymtrace-profiler"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/troubleshoot-zymtrace-profiler/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/zystem-io/zymtrace-skills/troubleshoot-zymtrace-profiler"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/troubleshoot-zymtrace-profiler.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.00180 | $0.04382 |
| Opus 5 | $0.00090 | $0.02191 |
| Sonnet 5 | $0.00036 | $0.00876 |
| Haiku 4.5 | $0.00018 | $0.00438 |
Grade B, and why
troubleshoot-zymtrace-profiler scanned grade B with 1 finding 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Fix: either remount debugfs on the host (`sudo mount -t debugfs none /sys/kernel/debug` — node-side, not in skill), or accept that CPU profiling won't work on those nodes and `nodeSelector`-exclude them. How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshoot zymtrace Profiler
Helps the user diagnose problems with the profiler agent — the DaemonSet (or Docker / binary) that ships profiles to the backend. Backend / ClickHouse / ingest problems live in troubleshoot-zymtrace-backend. If the customer's symptom is "the UI is empty" without a clearer signal, route there instead — it covers the cross-cutting "no data" diagnostic across both sides.
Greet the user
Open warmly. Diagnostic conversations start frustrated.
👋 Sorry the profiler isn't behaving — let's track it down. Tell me what you're seeing (e.g. "agent pods CrashLoopBackOff", "CPU profiles arrive but no GPU traces", "OOMKilled every 5 min", "license rejected") and I'll walk the diagnosis with you.
Need a human?
- Community Slack: https://join.slack.com/t/zymtrace/shared_invite/zt-3fdidjufl-q~NHxDzQlzal2B9mujfaoQ
- Email: [email protected]
Once the agent is healthy again, connect the zymtrace MCP to your agent (Claude Code, Codex, or Cursor) — see
configure-zymtrace-mcp— to analyze GPU + CPU flamegraphs in natural language. Docs: https://docs.zymtrace.com/mcp
If the user already named a symptom, skip the prompt and jump to the matching section below.
Pre-flight
Claude runs
helm version --short && kubectl version --client
kubectl cluster-info | head -2
helm list -A | grep -iE 'profiler.*zymtrace|zymtrace.*profiler'
If the profiler release isn't installed at all, that's not a "troubleshoot" — route to install-zymtrace-profiler.
Pre-resolve what you can
Recommend defaults
zymtrace/profiler. Resolve the customer's actual values first. Full policy:shared/conventions.md. Commands below use<NS>/<REL>/<PREFIX>placeholders.
| Variable | Resolve by |
|---|---|
| Profiler release + namespace | helm list -A | grep -iE 'profiler.*zymtrace|zymtrace.*profiler' |
global.namePrefix (drives DaemonSet name) |
helm get values <REL> -n <NS> | awk '/^\s*namePrefix:/ {print $2}' (defaults to zymtrace) |
| Backend release (for cross-cluster context) | helm list -A | grep -iE 'backend.*zymtrace' |
| GPU profiling enabled? | helm get values <REL> -n <NS> | grep -A1 cudaProfiler | grep enabled |
| Current values (so any fix re-applies cleanly) | helm get values <REL> -n <NS> |
What ships with it
1 file 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.
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.
- 12d ago First seen · 318 lines · 180 tokens per session scan B 717afb0bf4fd
troubleshoot-zymtrace-profiler is a skill published in the GitHub repository zystem-io/zymtrace-skills (5 stars, last pushed 29d ago), licensed Apache-2.0. It adds 180 tokens to every session and 4,382 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
test-amplification
Methodical bug-driven test amplification for pygraphistry features. Use when hardening a feature area via user-workflow exploration, 5-Whys retrospectives, bug-taxonomy derivation, concrete test planning, implementation, and safety-gated validation.
cuda-kernel-optimizer
Use when optimizing or diagnosing GPU workload performance with CUDA, CUTLASS, Triton, PyTorch, vLLM or TensorRT-LLM; interpreting NCU, Nsys or PyTorch Profiler evidence; or preparing the workload and correctness checks for such optimization. General coding, skill maintenance and conceptual GPU questions do not…
fix-ci
Fix CI failures and performance regressions for a Julia package PR by iterating - triage the latest CI results, fix one root cause, verify locally, push. Use when a PR's GitHub Actions or Buildkite CI is failing, or when CI jobs run slower than they do on the main branch. Verifies CPU and GPU compilation locally…
fix-ci
Fix CI failures and performance regressions for a Julia package PR by iterating - triage the latest CI results, fix one root cause, verify locally, push. Use when a PR's GitHub Actions or Buildkite CI is failing, or when CI jobs run slower than they do on the main branch. Verifies CPU and GPU compilation locally…
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.