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/expose-zymtrace-backend)<a href="https://agentmods.dev/skills/zystem-io/zymtrace-skills/expose-zymtrace-backend"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/expose-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/expose-zymtrace-backend"><img src="https://agentmods.dev/badge/skills/zystem-io/zymtrace-skills/expose-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.00160 | $0.02842 |
| Opus 5 | $0.00080 | $0.01421 |
| Sonnet 5 | $0.00032 | $0.00568 |
| Haiku 4.5 | $0.00016 | $0.00284 |
Grade A, and why
expose-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.
ERROR: ALB returns HTTP 464 to your `curl` — you set `backend-protocol: GRPC` instead of `backend-protocol: HTTP` + `backend-protocol-version: HTTP2`. Fix and re-apply. How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expose zymtrace Backend
Helps the user expose the gateway service externally. The zymtrace gateway is the single external surface — UI, ingest (gRPC), and symdb (HTTP) all flow through it.
Deep details (LoadBalancer one-liner, ACM cert lookup, cert-manager) live in ${CLAUDE_PLUGIN_ROOT}/skills/expose-zymtrace-backend/reference.md.
Backend must already be installed (
helm list -A | grep -i zymtraceshows a release). If not, useinstall-zymtrace-backend.
Sources of truth
- Live chart
values.yaml(ingress + gateway service keys): https://raw.githubusercontent.com/zystem-io/zymtrace-charts/main/charts/backend/values.yaml - Ingress doc: https://docs.zymtrace.com/install/backend/ingress
Pre-flight: verify the tools
Claude runs
helm version --short && kubectl version --client
kubectl cluster-info | head -2
helm list -A | grep -i zymtrace
kubectl get ingressclass
If helm/kubectl are missing → point to install docs; do not install them. If no zymtrace release exists → wrong skill, route to install-zymtrace-backend.
Pre-resolve what you can
Resolve namespace + release name first. Recommended defaults
zymtrace/backend; for an existing release use its namespace and name. Full policy:shared/conventions.md. Commands use<NS>and<REL>as placeholders.
| Variable | Resolve by |
|---|---|
| Existing release | helm list -A | grep -i zymtrace (one match → use it; multiple → ask) |
| Current values (so we layer onto them) | helm get values <REL> -n <NS> > current-values.yaml |
| Available ingress controllers | kubectl get ingressclass (alb / nginx / traefik) |
| AWS LBC installed? | kubectl get deploy -n kube-system aws-load-balancer-controller |
| Cloud / region (for ACM cert lookup) | kubectl config current-context → ARN parts; or aws configure get region |
| Existing ingress in this NS | kubectl get ingress -n <NS> |
Things you must ask:
- Which exposure mode (table below)?
- Hostname (for ingress paths).
- TLS source (ACM cert ARN for ALB / cert-manager issuer for NGINX / existing TLS secret).
What ships with it
5 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 · 197 lines · 160 tokens per session scan A ab1651b8f079
expose-zymtrace-backend is a skill published in the GitHub repository zystem-io/zymtrace-skills (5 stars, last pushed 27d ago), licensed Apache-2.0. It adds 160 tokens to every session and 2,842 once invoked, about $0.0008 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
apify-actor-development
Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
dstack-prototyping
Use with the dstack skill for model-serving work when the image, serving command, resources, backend/fleet choice, or service behavior is not proven. Guides task-first prototyping on real hardware, choosing fleets/backends that can reuse idle instances and caches, checking vLLM/SGLang sources, and verifying the final…
enterprise
Enterprise-grade systems with microservices, Kubernetes, Terraform, and AI Native methodology. For multi-feature initiatives spanning a release timeline, combine with /sprint master-plan (v2.1.13) to group features into a single 8-phase sprint container with shared scope/budget and 4 auto-pause triggers…
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-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.