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.
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 skills add NVIDIA/nvcf --skill nvcf-explore-stackgit 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/nvcf-explore-stack)<a href="https://agentmods.dev/skills/nvidia/nvcf/nvcf-explore-stack"><img src="https://agentmods.dev/badge/skills/nvidia/nvcf/nvcf-explore-stack/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/nvidia/nvcf/nvcf-explore-stack"><img src="https://agentmods.dev/badge/skills/nvidia/nvcf/nvcf-explore-stack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00161 | $0.01553 |
| Opus 5.5 | $0.00064 | $0.00621 |
| Sonnet 5.5 | $0.00032 | $0.00311 |
| Haiku 4.5 | $0.00016 | $0.00155 |
Grade A, and why
nvcf-explore-stack 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NVCF Explore Stack
Help a user or developer navigate the NVCF self-hosted stack inside the monorepo. Identify what a release is, what installs it, what it depends on, and which subtree owns the chart and the runtime image.
Instructions
This skill is for both NVCF users and NVCF developers. Users use it to understand stack dependencies, deployment order, and CI/CD migration questions. Developers use it to find the owning chart, source subtree, hook, or helmfile stage before making changes.
Use this skill long enough to answer the question, then hand off to the right execution skill. Always cite the source file path so the user can verify.
Required inputs
Read these from the monorepo root.
Authoritative (always read first when answering):
deploy/stacks/self-managed/helmfile.d/00-observability-infrastructure.yaml.gotmpldeploy/stacks/self-managed/helmfile.d/01-dependencies.yaml.gotmpldeploy/stacks/self-managed/helmfile.d/02-core.yaml.gotmpldeploy/stacks/self-managed/helmfile.d/03-observability.yaml.gotmpldeploy/stacks/observability/helmfile.d/01-observability.yaml.gotmpldeploy/stacks/nvcf-compute-plane/helmfile.d/01-dependencies.yaml.gotmpldeploy/stacks/nvcf-compute-plane/helmfile.d/02-nvca.yaml.gotmpl
Chart-level (when the chart is checked into the monorepo):
deploy/helm/<chart>/Chart.yamldeploy/helm/<chart>/values.yaml
Common questions
What deploys X
: Look up release X in the helmfile stage files. Return chart name, version, namespace, and which gotmpl file declares it. If the chart is checked in, also point at deploy/helm/<chart>/.
What does X depend on
: Return the needs: chain for that release plus the stage gate it sits behind (control-plane stages 0 -> 1 -> 2 -> 3, then compute-plane). Include any profile, condition:, or component mode that gates whether X deploys at all.
What hooks run for X
: Read the checked-in chart under deploy/helm/<chart>/ when available. Search its templates/ directory for Helm hook annotations, weights, hook events (pre-install / post-install), images used, and purpose. Cite the chart-relative template file path. If the chart is not checked in, cite its Helmfile chart reference and state that local templates are unavailable.
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 · +1 lines e26f9b6cc884
- 13d ago Changed · +3 lines 64dae63cb250
- 24d ago Changed 848f0f7e1bc3
- 1mo ago Changed 3029461e358e
- 1mo ago First seen · 104 lines · 161 tokens per session scan A d0b5927fcd15
nvcf-explore-stack is a skill published in the GitHub repository NVIDIA/nvcf (238 stars, last pushed today), licensed Apache-2.0. It adds 161 tokens to every session and 1,553 once invoked, about $0.0006 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.
Other skills, from other repositories
securing-helm-chart-deployments
Secure Helm chart deployments by validating chart integrity, scanning templates for misconfigurations, and enforcing security contexts in Kubernetes releases.
04-security
A security and operations guide for deploying Dify, an open-source platform for building AI applications, in production.
modal
Use when running Python or GPU workloads serverlessly on Modal — modal.App, inline container Images, gpu= on @app.function, Volumes for weight caching, Cron schedules, ASGI endpoints, modal run vs serve vs deploy. NOT managed prediction APIs with no container of your own (that is replicate); NOT SSH-able GPU boxes…
olares-chart
Olares app packaging and chart authoring via olares-cli chart — port a repo, docker-compose, or generic Helm chart; build/push the image; author, lint, package, and deploy an OlaresManifest; wire storage, middleware, entrances, env, and GPU; edit the chart after diagnosis. Runtime failure diagnosis is olares-doctor…
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.