NVIDIA/skills is a catalogue of portable instruction sets that teach coding agents how to use NVIDIA software for robotics, simulation, CUDA, retrieval-augmented generation, and related workflows. Developers install these skills in agents such as Claude Code or Codex, while the catalogue mirrors skills maintained in separate NVIDIA product repositories.
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/skills --skill doca-container-deploymentgit clone --depth 1 https://github.com/NVIDIA/skillsWrote 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/skills/doca-container-deployment)<a href="https://agentmods.dev/skills/nvidia/skills/doca-container-deployment"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-container-deployment/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/skills/doca-container-deployment"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-container-deployment.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.00231 | $0.02670 |
| Opus 5.5 | $0.00092 | $0.01068 |
| Sonnet 5.5 | $0.00046 | $0.00534 |
| Haiku 4.5 | $0.00023 | $0.00267 |
Grade A, and why
doca-container-deployment 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 8d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCA container deployment
Examples
- "How do I run a DOCA service container on BlueField?" — this is in scope after the setup recognize front door. Drop a documented pod spec; do not invent YAML or image tags.
- "The pod spec is in the directory but the pod never starts." — walk the eight-layer taxonomy before letting kubelet restart-loop the pod.
Instructions
Follow Loading order below. Open the tasks companion for configure / run / debug. Open the capabilities companion for the kubelet-standalone contract. Do not open every companion file.
Where to start: This skill is for operating the cross-cutting DOCA container-deployment runtime — the shared pattern every DOCA service on the BlueField uses to come up (kubelet standalone agent on the BlueField Arm watching a static-pod manifests directory; the operator drops a YAML pod spec into that directory; kubelet schedules the pod and runs the container).
If the developer has NOT yet decided container vs. bare-metal
("I just got a BlueField, what now?", "my code is built, how do I
run it?", "how do I deploy this?"), route them BACK to
doca-setup/SKILL.md first.
That is the front-door routing decision. The wrong failure mode is
to silently push every developer onto the container path because the
agent loaded this skill first. ## recognize detects the system
shape, asks the minimum residual question, and lands the developer on
either this skill (when the workload is a packaged DOCA service to
drop on a BlueField) or the bare-metal-path sibling
doca-bare-metal-deployment/SKILL.md
(when the workload is a DOCA-linked application binary the developer
launches directly).
If the developer is already on the container path, open
the tasks companion and start at
## configure. If the question is what shape
of runtime is this and what does the deployment contract look like,
start at the capabilities companion. For per-service
overlays, follow the per-service skill under skills/services/ that
layers on top of this one — the supported overlays are Argus, DMS,
Firefly, and UROM service. Flow-Inspector and OS-Inspector are
outside this bundle's scope; route them through
doca-public-knowledge-map/SKILL.md
instead of applying this runtime overlay. Externally-productized
NVIDIA services (BlueMan, HBN, SNAP, Virtio-net, DOCA Telemetry
Service as productized, …) are also out of scope and route through
that map. If DOCA is
not installed on the BlueField target yet, route to
doca-setup/SKILL.md first.
What ships with it
7 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.
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.
- 8d ago Changed 9540fe088528
- 15d ago Changed · +1 lines 9ac56d5e7010
- 23d ago Changed · +36 lines · -3 tokens per session f0360f49b657
- 2mo ago First seen · 195 lines · 234 tokens per session scan A 20274f090dce
doca-container-deployment is a skill published in the GitHub repository NVIDIA/skills (3,873 stars, last pushed yesterday), licensed Apache-2.0. It adds 231 tokens to every session and 2,670 once invoked, about $0.0009 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.
doca-container-deployment compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| doca-container-deploymentNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 231 | Claude Code, Codex |
| self-hosted-stackmakifbaysal/tasktrooper | Skill | 120 | 16d ago | Apache-2.0 | A | 70 | Claude Code, Codex |
| supply-chain-and-dependency-reviewmakifbaysal/tasktrooper | Skill | 120 | 16d ago | Apache-2.0 | C | 90 | Claude Code, Codex |
| keloskelos-dev/kelos | Skill | 354 | yesterday | Apache-2.0 | A | 128 | Claude Code, Codex |
| kubernetes-operationsWrongStack/WrongStack | Skill | 404 | yesterday | MIT | A | 102 | Claude Code |
| screen-mockup-htmlmakifbaysal/tasktrooper | Skill | 120 | 16d ago | Apache-2.0 | A | 63 | Claude Code, Codex |
| responsive-layoutmakifbaysal/tasktrooper | Skill | 120 | 16d ago | Apache-2.0 | A | 35 | Claude Code, Codex |