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/deepops/diagnose-driver-installnpx skills add NVIDIA/deepops --skill diagnose-driver-installgit clone --depth 1 https://github.com/NVIDIA/deepopsWhat 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.00047 | $0.00762 |
| Opus 5 | $0.00023 | $0.00381 |
| Sonnet 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 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 — 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.
- 2d 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,471 stars, last pushed today), licensed BSD-3-Clause. It adds 47 tokens to every session and 762 once invoked, about $0.0002 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
dce-edge
DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render / stream-utils for edge builds. Covers if/else branching for webpack DCE, TypeScript definite assignment, the NEXTRUNTIME…
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
land-and-deploy
Land and deploy workflow. (gstack).
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…