DeepOps is a collection of automation tools for deploying and managing compute clusters that use NVIDIA GPUs with Kubernetes or Slurm. It supports environments ranging from full data-center clusters to individual machines needing GPU drivers, Docker, and NVIDIA container support.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/NVIDIA/deepopsnpx agentmods add skills/nvidia/deepops/diagnose-driver-installWrote 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/deepops/diagnose-driver-install)<a href="https://agentmods.dev/skills/nvidia/deepops/diagnose-driver-install"><img src="https://agentmods.dev/badge/skills/nvidia/deepops/diagnose-driver-install/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/deepops/diagnose-driver-install"><img src="https://agentmods.dev/badge/skills/nvidia/deepops/diagnose-driver-install.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.00047 | $0.00762 |
| Opus 5.5 | $0.00019 | $0.00305 |
| Sonnet 5.5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
diagnose-driver-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 1mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose an NVIDIA driver install
Work through these in order; most "driver failures" are one of the first three and need no reinstall.
1. Are you being fooled by GPU hiding?
On DeepOps Slurm nodes, GPUs are hidden from ordinary SSH sessions by
design. Bare nvidia-smi over SSH reporting No devices were found on an
otherwise healthy node is expected.
srun --gpus=1 nvidia-smi # the authoritative test on Slurm nodes
If the srun job sees the GPU, the driver is fine. Stop here.
2. Is the hardware visible at all?
lspci | grep -i nvidia
No output → not a driver problem. The GPU is absent, unseated, or bound by VFIO passthrough or platform firmware; escalate to hardware support before touching software.
3. Open vs proprietary kernel modules
nvidia-smi: No devices were found immediately after a clean install is the
classic symptom of the wrong module flavor for the GPU generation:
- Turing and newer (T4, A100, H100, RTX PRO Blackwell): open kernel modules
supported — DeepOps default
nvidia_driver_ubuntu_use_open_kernel_modules: trueis correct. - Pascal and older (P100, GTX 10xx): open modules are not supported —
set
nvidia_driver_ubuntu_use_open_kernel_modules: falseinconfig/group_vars/all.ymland rerun the driver play.
Check what is loaded: modinfo nvidia | grep -i license (open modules say
MIT/GPL, proprietary says NVIDIA).
4. Did the kernel module actually build and load?
dkms status # driver module state per kernel
dmesg | grep -iE 'nvidia|nvrm' | tail -20
lsmod | grep nvidia
- DKMS shows an error for the running kernel → usually missing headers
(
linux-headers-$(uname -r)) or a kernel updated after the driver install. Install headers or reboot into the matching kernel, then rerun the driver play. - Module loaded but
nvidia-smifails → checkdmesgfor RmInitAdapter or fallen-off-the-bus errors; these are hardware/firmware territory.
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.
- 1mo ago First seen · 83 lines · 47 tokens per session scan A b26eb40826be
diagnose-driver-install is a skill published in the GitHub repository NVIDIA/deepops (1,478 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 47 tokens to every session and 762 once invoked, about $0.0002 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
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Remote or non-C++ control…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when the device is managed by Catalyst Center and you want its…
pyats-troubleshoot
Systematic network troubleshooting - connectivity, routing, interface, protocol, and performance issues using structured OSI-layer and divide-and-conquer methodology, via direct CLI/pyATS access. Use when something is broken, a device is unreachable, a link is flapping, users report slow performance, or an OSPF/BGP…