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-values-customizationnpx skills add NVIDIA/nvcf --skill nvca-values-customizationgit 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.00051 | $0.00810 |
| Opus 5 | $0.00026 | $0.00405 |
| Sonnet 5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
nvca-values-customization 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customizing NVCA Operator Chart Values
Use this skill from deploy/helm/nvca-operator.
Values Flow
src/compute-plane-services/nvca/deployments/nvca-operator/ source chart
-> scripts/ci_vendor_nvca_operator_chart applies self-managed defaults
-> nvca-operator/values.yaml vendored chart values
-> scripts/render_values_from_stack_env.sh stack-aware generated values
-> make install or make install-from-stack optional additional overrides
Permanent Defaults
For defaults that every self-managed deployment should receive, edit
scripts/ci_vendor_nvca_operator_chart and re-vendor:
make vendor-chart
git diff nvca-operator/values.yaml
The vendoring script already applies defaults such as:
ngcConfig.clusterSource = "self-managed"ngcConfig.serviceKey = "dummy-api-key"image.tagremains empty so templates use the published chart versionselfManaged.nvcaVersion = "$NVCA_VERSION"generateImagePullSecret = falseselfManaged.sharedStorage.imageTag = "$NVCA_SHARED_STORAGE_IMAGE_TAG"nameOverride = "nvca-operator"fullnameOverride = "nvca-operator"
Do not edit nvca-operator/values.yaml directly for a permanent default. The
next vendor run will overwrite it.
Deploy-time Overrides
Use additional_values for one-off validation or environment-specific values:
make install-from-stack \
stack_repo=../../../deploy/stacks/self-managed \
stack_env=local \
additional_values=override.yml
Use deploy-time overrides for secrets, credentials, cluster-specific IDs, and temporary validation changes.
Adding .env Inputs
For version-like values that the vendoring script needs, add a variable to
.env, require it in scripts/ci_vendor_nvca_operator_chart, and re-vendor:
MY_NEW_CONFIG=some-value
update_yaml_key ".myConfig = \"${MY_NEW_CONFIG:?MY_NEW_CONFIG is not set}\"" "${TARGET_DIR}/values.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 · 102 lines · 51 tokens per session scan A d8eb95fc398f
nvca-values-customization is a skill published in the GitHub repository NVIDIA/nvcf (202 stars, last pushed 2d ago), licensed Apache-2.0. It adds 51 tokens to every session and 810 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
test-skill
A minimal test skill for e2e testing of the skill pack resolver.
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…
buy-x402
Buy from any x402-gated endpoint. Start with go — it probes, detects the offer type, and runs the right flow. Expert flows underneath: pay for one-shot HTTP services (single authorization, no sidecar), pay-agent for one-shot streaming agent calls, and buy for long-running paid inference (pre-authorized batch via…
obol-stack-dev
CLI-first Obol Stack development and QA runbook. Use when working on obol-stack lifecycle, obol CLI surfaces, x402 seller/buyer tests, live Base Sepolia OBOL smoke, Anvil fork regressions, ERC-8004 registration, LiteLLM paid routing, release-smoke, cloudflared, Renovate image bumps, or remote QA worktrees.
bridging
Move assets between Ethereum L1 and L2s — canonical Arbitrum-style bridges (Arbitrum One, Robinhood Chain), Base's OP-stack bridge, and fast third-party routes (Across, CCIP). Quote the full round trip before moving anything: canonical deposits take 10-15 min, canonical withdrawals lock capital for 7 DAYS plus an L1…
building-blocks
DeFi legos and protocol composability on Ethereum and L2s. Major protocols per chain — Aerodrome on Base, GMX/Pendle on Arbitrum, Velodrome on Optimism — plus mainnet primitives (Uniswap, Aave, Compound, Curve). How they work, how to build on them, and how to combine them. Use when building DeFi integrations, choosing…