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/upgrade-zymtrace-backend)<a href="https://agentmods.dev/skills/zystem-io/zymtrace-skills/upgrade-zymtrace-backend"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/upgrade-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/upgrade-zymtrace-backend"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/upgrade-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.00143 | $0.04204 |
| Opus 5 | $0.00072 | $0.02102 |
| Sonnet 5 | $0.00029 | $0.00841 |
| Haiku 4.5 | $0.00014 | $0.00420 |
Grade A, and why
upgrade-zymtrace-backend scanned grade A 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Gateway responds: `curl -fsI http://<host>` returns 2xx/3xx/4xx (not 5xx / connection-refused / timeout). How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade zymtrace Backend
Helps the user upgrade an already-installed zymtrace backend. Three paths:
| Path | What changes | When to use |
|---|---|---|
| A. Image-only bump | services.common.imageTag (and pulled image) |
Apply a patch/hotfix on the same chart. Lowest risk. |
| B. Chart version bump | Helm chart version + templates + defaults | New chart features, schema additions, new config keys. |
| C. Combined | Chart + image together | The common case for moving between zymtrace minor/major releases. |
Deep details (backup, rollback, schema migrations, the migrate job) live in ${CLAUDE_PLUGIN_ROOT}/skills/upgrade-zymtrace-backend/reference.md.
Fresh install? Use the
install-zymtrace-backendskill instead.
Sources of truth
- Live
values.yaml: https://raw.githubusercontent.com/zystem-io/zymtrace-charts/main/charts/backend/values.yaml - Chart releases (versions & appVersions):
helm search repo zymtrace/backend --versions - Docs: https://docs.zymtrace.com/install/backend/helm-docker
- Latest release + what changed (resolve "latest", diff current→target; fallback for the latest version when
helm searchcan't): https://docs.zymtrace.com/changelog (newest at the top)
Pre-flight: verify the tools
Claude runs
helm version --short && kubectl version --client
kubectl cluster-info | head -2
helm list -A | grep -i zymtrace
If helm/kubectl are missing → point to install docs; do not install for them. If helm list -A | grep -i zymtrace shows no zymtrace release → wrong skill, route to install-zymtrace-backend.
Check for a customer-provided values file
Before any chart-version bump (Path B / C), ask:
Do you have the values file Zymtrace originally sent you (often named
custom-values.yaml,backend-values.yaml, or<company>-values.yaml)?
If yes → use that file directly with helm upgrade --install ... -f <their-file>. Read it first to confirm it matches what's currently deployed (helm get values <REL> -n <NS>).
What ships with it
2 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.
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.
- 11d ago First seen · 272 lines · 143 tokens per session scan A da9046596d6b
upgrade-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 143 tokens to every session and 4,204 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
nvcf-self-managed-prerequisite
Install the prerequisites the NVCA operator / compute plane needs before nvcf-nvca-install can succeed: the operator tool nvcf-cli (required by the compute-plane stack's register-cluster step), KAI Scheduler (for the KAIScheduler feature gate), and the SMB CSI driver (for the sharedStorage Samba sidecar PVCs). The two…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
nvca-values-customization
Customize NVCA Operator Helm chart values in the native monorepo. Use when modifying vendored defaults, changing stack-derived install values, adding deployment-time overrides, or updating scripts under deploy/helm/nvca-operator.
nvca-self-managed-install
Install or validate the NVCA Operator chart against a self-managed NVCF control plane from the native monorepo. Use when the control plane comes from deploy/stacks/self-managed and NVCA must be installed with stack-derived image repository settings.
tao-run-on-brev
Run a TAO training/evaluation/inference container on an NVIDIA Brev GPU instance. Instance provisioning (create/search/stop/delete/login) is delegated to the official brev-cli agent skill or the Brev MCP server; this skill covers only the TAO-specific part — running the container over brev exec via the four-verb…
gpu-server-setup
Prepare a Linux server with NVIDIA GPUs for neural-network and LLM workloads, or diagnose one that misbehaves. Use when the user asks to set up or prepare a GPU server, install NVIDIA drivers or CUDA on Debian/Ubuntu, wire Docker to GPUs (NVIDIA Container Toolkit), deploy vLLM / Infinity / OpenWebUI / Ollama /…