What is nvcf-self-managed-cli?

A command-line workflow for installing, managing, checking, and removing self-hosted NVIDIA Cloud Functions deployments. Self-hosted means the software runs on infrastructure you operate.

Use it to register clusters, install control and compute planes, deploy or invoke functions, manage tasks and keys, rotate authentication keys, check health, or uninstall NVCF.

It puts cluster setup and day-to-day operations into one documented workflow, including diagnosis when an installation fails.

nvcf-self-managed-cli — Skill for Claude Code by NVIDIA/nvcf

About the project

NVIDIA Cloud Functions is a platform for deploying, managing, and running GPU-based workloads such as inference, streaming, and batch processing, while routing requests to GPU worker clusters. Its monorepo contains the service code, deployment materials, documentation, examples, command-line tools, agent skills, and validation tools used to build and operate the platform.

NVIDIA/nvcf · 244 stars · on GitHub · docs.nvidia.com

Install

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.

Any agent

npx skills add NVIDIA/nvcf --skill nvcf-self-managed-cli

Clone the repo

git clone --depth 1 https://github.com/NVIDIA/nvcf

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nvidia/nvcf/nvcf-self-managed-cli/github.svg)](https://agentmods.dev/skills/nvidia/nvcf/nvcf-self-managed-cli)

Your own site

<a href="https://agentmods.dev/skills/nvidia/nvcf/nvcf-self-managed-cli"><img src="https://agentmods.dev/badge/skills/nvidia/nvcf/nvcf-self-managed-cli/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nvidia/nvcf/nvcf-self-managed-cli"><img src="https://agentmods.dev/badge/skills/nvidia/nvcf/nvcf-self-managed-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 193 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,922 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 5 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Prompt Injection · line 18
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
high Privilege Escalation · line 52
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
high Privilege Escalation · line 233
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
high Privilege Escalation · line 56
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
medium Rogue Agent · line 201
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00193	$0.06922
Opus 5.5	$0.00077	$0.02769
Sonnet 5.5	$0.00039	$0.01384
Haiku 4.5	$0.00019	$0.00692

Measured yesterday against content hash c4362f1ae9cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

nvcf-self-managed-cli 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 yesterday.

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.

ai-tooling/user/skills/nvcf-self-managed-cli/SKILL.md · 343 lines

How it starts

The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NVCF Self-Hosted CLI

nvcf-cli drives every step of bringing up self-hosted NVIDIA Cloud Functions: cluster registration, control-plane install, compute-plane install, function deploy/invoke, and lifecycle management. Use this skill any time the user wants to operate self-hosted NVCF.

When to use

"install self-hosted NVCF" / "bring up an NVCF cluster"
"register a (compute|GPU) cluster with NVCF"
"deploy a (container|GPU) function" / "invoke an NVCF function"
"check NVCF cluster health" / "is my NVCF install OK?"
"rotate NVCF cluster JWKS" / "the NVCA agent stopped authenticating"
"tear down NVCF" / "remove the compute plane" / "uninstall NVCF" / "deregister this cluster"
"preview what down would do" / "dry-run uninstall"
Any task operation: create / run / submit / monitor / cancel / delete / list tasks, helm task, update task secrets, retrieve task results, bulk fetch task details.
Any reference to NVCT, NVCT task, or NVCT batch job (list / run / cancel / delete / results).
Any reference to NVCFBackend, NVCA, ICMS, helm releases like helm-nvcf-*, or icms.<domain> / api.<domain> URLs.

Quick start

For remote one-click installs, prepare Gateway API ingress and CLI endpoint configuration before running self-hosted up. The command applies the control plane and then immediately calls API, API Keys, invocation, and gRPC endpoints. If the Gateway is not programmed or the CLI host headers do not match the HTTPRoutes rendered by the stack environment, post-install health and cluster registration will fail.

# Single-cluster (control + compute on the current kubeconfig context):
nvcf-cli self-hosted up --cluster-name=ncp-local

# Split-cluster (control plane on context A, compute plane on context B):
KUBECONFIG=cp.yaml:gpu1.yaml nvcf-cli self-hosted up \
  --cluster-name=ncp-local \
  --control-plane-context=admin@cp \
  --compute-plane-context=admin@gpu1 \
  --icms-url=https://icms.nvcf.example.com

# Add a new compute plane to an existing control plane, from the profile
# `self-hosted control-plane profile export` wrote to the path it printed,
# copied here as control-plane-profile.yaml (no kubectl access to CP needed;
# reaches the control plane via the public ICMS HTTPRoute):
nvcf-cli self-hosted compute-plane register \
  --control-plane-profile=control-plane-profile.yaml \
  --cluster-name=ncp-local-2 \
  --kube-context=admin@gpu2 \
  --icms-url=https://icms.nvcf.example.com \
  --token=$ADMIN_JWT \
  --output=ncp-local-2-register-values.yaml
nvcf-cli self-hosted compute-plane install \
  --values=ncp-local-2-register-values.yaml \
  --kube-context=admin@gpu2 \
  --cluster-name=ncp-local-2

# Tear down (always plan-only first):
nvcf-cli self-hosted down --plan-only --cluster-name=ncp-local --json | jq
nvcf-cli self-hosted down --cluster-name=ncp-local

# Per-plane uninstall (GitOps; mirrors `install`):
nvcf-cli self-hosted uninstall --no-apply --compute-plane --cluster-name=ncp-local | kubectl delete -f -

Read the full file on GitHub · 343 lines

Files

What ships with it

13 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.

Changes

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.

yesterday Changed · +9 lines c4362f1ae9cf
13d ago Changed · +13 lines 4b8e3035298e
14d ago Changed 9557c048ecbc
1mo ago Changed aa9f7e246f38
1mo ago Changed · +5 lines 1c05f8016953
1mo ago First seen · 316 lines · 193 tokens per session scan A c4f288f62e50

Subscribe to this mod's changes

nvcf-self-managed-cli is a skill published in the GitHub repository NVIDIA/nvcf (244 stars, last pushed today), licensed Apache-2.0. It adds 193 tokens to every session and 6,922 once invoked, about $0.0008 per session on Opus 5.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.

Cloud DevOps and cloud GPU NVIDIA cloud-functions inference kubernetes serverless-gpu

tao-run-on-kubernetes

Kubernetes execution platform — submits TAO container jobs as k8s Jobs with NVIDIA GPU scheduling; single-pod for one node, Indexed Jobs for multi-node distributed training. Use when running on EKS / GKE / AKS / on-prem clusters with the NVIDIA GPU Operator installed, or when integrating TAO into an existing…

NVIDIA-TAO/tao-skill-bank · 80 tokens

vmware-privateai

Use this skill whenever the user needs the GPU / AI-infrastructure layer of VMware Private AI Foundation with NVIDIA (PAIF-N) on vSphere 9.x / VCF 9.1: inventory GPU hosts and physical GPU devices, see which VMs consume a vGPU and the profile each holds, read real-time GPU utilization, list the vGPU and DirectPath…

vmware-skills/VMware-PrivateAI · 237 tokens

nvcf-self-managed-cli