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 agentmods add skills/nvidia/nvcf/nvca-chart-releasenpx skills add NVIDIA/nvcf --skill nvca-chart-releasegit clone --depth 1 https://github.com/NVIDIA/nvcfWhat 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 | $0.00061 | $0.01005 |
| Opus 5 | $0.00030 | $0.00502 |
| Sonnet 5 | $0.00012 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
nvca-chart-release 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NVCA Operator Chart Release Workflow
Propagates Helm chart changes through the native monorepo paths:
| Component | Path | Purpose |
|---|---|---|
| NVCA source | src/compute-plane-services/nvca |
Operator and agent source plus source chart at deployments/nvca-operator/ |
| Vendored chart | deploy/helm/nvca-operator |
Vendors the source chart, applies self-managed defaults, publishes helm-nvca-operator |
| Self-managed stack | deploy/stacks/self-managed |
Control-plane Helmfile deployment and environment defaults |
Workflow
-
Make source changes in
src/compute-plane-services/nvcawhen operator, agent, or source chart behavior changes. Test them there. -
Vendor from the monorepo source chart at
src/compute-plane-services/nvca/deployments/nvca-operator/. -
Set the version inputs, either in the environment or in
deploy/helm/nvca-operator/.env:NVCA_OPERATOR_VERSION=<operator-image-tag> NVCA_VERSION=<agent-image-tag> NVCA_SHARED_STORAGE_IMAGE_TAG=<shared-storage-tag> -
Vendor and validate from
deploy/helm/nvca-operator:make vendor-chart make lint make template make validate -
If the chart is tested against a local self-managed control plane, render stack-aware values and install from this chart subtree:
make render-values-from-stack stack_repo=../../../deploy/stacks/self-managed stack_env=local make install-from-stack stack_repo=../../../deploy/stacks/self-managed stack_env=localUse
additional_values=override.ymlfor one-off validation. Do not edit the stack just to test this chart.
CI and Release
Umbrella CI is declared in tools/ci/subproject-validations.yaml with
subproject id nvca-operator. Do not add a chart-local .gitlab-ci.yml.
Validate the same chart path CI uses:
tools/ci/validate-helm-chart deploy/helm/nvca-operator/nvca-operator \
-f tools/ci/helm-validate-values/nvca-operator.yaml
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.
- 2d ago First seen · 105 lines · 61 tokens per session scan A fae474ff0103
nvca-chart-release is a skill published in the GitHub repository NVIDIA/nvcf (202 stars, last pushed 2d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,005 once invoked, about $0.0003 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
release-chart
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump Chart.yaml/artifacthub-pkg.yml/values.yaml, regenerate docs, tag the release so CI publishes it). Trigger on requests like "release…
obol-stack
Monitor the Kubernetes cluster running the Obol Stack. Use when asked about pod status, logs, services, events, deployments, or diagnosing issues. Read-only access to own namespace via ServiceAccount.
kubernetes
Kubernetes orchestration authority — pods, deployments, services, ingress, helm charts, kustomize overlays, RBAC, network policies, operators, StatefulSets for databases, production-grade cluster hardening, and kubectl workflows.
helm-expert
Expert-level Helm 3 package management, chart development, templating, and production operations.
helm
Skill "helm" from chaterm/terminal-skills, covering helm 包管理, 概述, 基础命令, 仓库管理 and 添加仓库.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.