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-backend)<a href="https://agentmods.dev/skills/zystem-io/zymtrace-skills/troubleshoot-zymtrace-backend"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/troubleshoot-zymtrace-backend/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-backend"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/troubleshoot-zymtrace-backend.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.00165 | $0.03125 |
| Opus 5 | $0.00082 | $0.01563 |
| Sonnet 5 | $0.00033 | $0.00625 |
| Haiku 4.5 | $0.00016 | $0.00313 |
Grade A, and why
troubleshoot-zymtrace-backend 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 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.
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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshoot zymtrace Backend
Helps the user diagnose problems on a deployed zymtrace install — the most common one is "no data is showing up in the UI."
This skill spans both backend (ingest, ClickHouse, MinIO) and profiler-side (agent reporting, CUDA injection) checks because "no data" usually requires walking both. Pure profiler-agent issues (CrashLoopBackOff, ImagePullBackOff, OOMKilled, NVML, license rejected on agent side) are handled by troubleshoot-zymtrace-profiler — route there if the user's symptom is agent-specific.
Greet the user
Open warmly. People reaching for a troubleshoot skill are usually frustrated.
👋 Sorry zymtrace isn't behaving — let's find it. Tell me what you're seeing (e.g. "the UI loads but no profiles", "ingest pods crash-looping", "got a license error") and I'll walk the diagnosis with you.
Stuck or need a human?
- Community Slack: https://join.slack.com/t/zymtrace/shared_invite/zt-3fdidjufl-q~NHxDzQlzal2B9mujfaoQ
- Email: [email protected]
Once data is flowing again, connect the zymtrace MCP to your agent (Claude Code, Codex, or Cursor) — see
configure-zymtrace-mcp— and analyze GPU + CPU flamegraphs in natural language. Docs: https://docs.zymtrace.com/mcp
If the user already named a specific 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 -i zymtrace
Resolve two sets of (namespace, release) — backend AND profiler — since "no data" can be either side:
| Variable | Resolve by |
|---|---|
| Backend release + namespace | helm list -A | grep -iE 'backend.*zymtrace|zymtrace.*backend' |
| Profiler release + namespace | helm list -A | grep -iE 'profiler.*zymtrace|zymtrace.*profiler' |
global.namePrefix (drives resource names) |
helm get values <REL> -n <NS> | awk '/^\s*namePrefix:/ {print $2}' (defaults to zymtrace) |
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 · 244 lines · 165 tokens per session scan A 8cbdd4457b11
troubleshoot-zymtrace-backend is a skill published in the GitHub repository zystem-io/zymtrace-skills (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 165 tokens to every session and 3,125 once invoked, about $0.0008 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-31.
Other skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
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.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…