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-self-managed-installnpx skills add NVIDIA/nvcf --skill nvca-self-managed-installgit clone --depth 1 https://github.com/NVIDIA/nvcfWrote 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/nvidia/nvcf/nvca-self-managed-install)<a href="https://agentmods.dev/skills/nvidia/nvcf/nvca-self-managed-install"><img src="https://agentmods.dev/badge/skills/nvidia/nvcf/nvca-self-managed-install.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.00656 |
| Opus 5 | $0.00028 | $0.00328 |
| Sonnet 5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
nvca-self-managed-install 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 4d 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.
What it actually says
NVCA Self-Managed Install
Use deploy/helm/nvca-operator as the install surface for NVCA Operator chart
validation. Do not add NVCA back into the stack Helmfile just to test this
chart.
Source of Truth
- Control-plane deployment:
deploy/stacks/self-managed - NVCA chart and install workflow:
deploy/helm/nvca-operator - NVCA source images and source chart:
src/compute-plane-services/nvca - Cluster prerequisites: use the public
nvcf-self-managed-prerequisiteskill - Full stack install and teardown: use the public
nvcf-self-managed-installationskill
Preferred Workflow
Run from deploy/helm/nvca-operator:
make render-values-from-stack \
stack_env=local \
stack_repo=../../../deploy/stacks/self-managed
Inspect the generated file under bin/, then install or upgrade:
make install-from-stack \
stack_env=local \
stack_repo=../../../deploy/stacks/self-managed
Optional Inputs
additional_values=override.ymlfor one-off overridesNCA_ID=<value>to set the primary account ID explicitlyCLUSTER_NAME=<value>andCLUSTER_ID=<value>to preserve or pin cluster identityIMAGE_PULL_SECRET_NAME=<secret>to attach a pre-created image pull secret
Existing Release Reuse
If nvca-operator is already installed in the nvca-operator namespace, the
render helper reuses current release values first, then overlays repository
paths derived from the stack environment file. Use this to preserve cluster IDs
and operator settings during upgrades.
Safety
Before creating, deleting, or reusing local k3d clusters, read the local-dev
safety guidance in .cursor/skills/nvcf-self-hosted-local-dev/SKILL.md from
the repo root. Do not delete clusters or Helm releases without explicit user
approval.
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.
- 4d ago First seen · 72 lines · 55 tokens per session scan A 9d9d56afc42c
nvca-self-managed-install is a skill published in the GitHub repository NVIDIA/nvcf (202 stars, last pushed 4d ago), licensed Apache-2.0. It adds 55 tokens to every session and 656 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
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.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
kubernetes-ontology-access
Use this skill whenever a user wants to onboard, deploy, install, or operate kubernetes-ontology; set up its Helm chart, release CLI, daemon, or topology viewer; run Kubernetes topology queries; diagnose Pod or Workload failures with AI-agent workflows; or connect human visual troubleshooting to the CLI and HTTP API.…
kubernetes-mesh-provisioner
Kubernetes Mesh Provisioner atomic skill. Stands up an RKE2 cluster (server + agents) with Cilium CNI and the NVIDIA GPU device plugin, the Kubernetes parallel of swarm-mesh-provisioner. Idempotent — re-runnable.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
image-pull-debug
Diagnose container image pull failures (ErrImagePull / ImagePullBackOff). Checks pod status, containerd logs, and events to identify root cause.