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/deploy-slurm-clusternpx skills add NVIDIA/deepops --skill deploy-slurm-clustergit 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.00042 | $0.00625 |
| Opus 5 | $0.00021 | $0.00313 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
deploy-slurm-cluster 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy a Slurm GPU cluster
Preconditions
- Ubuntu 22.04/24.04 or RHEL/Rocky 8/9 hosts you may fully manage (driver installs may reboot them; no active users or workloads).
- SSH access from the provisioning machine to every host as a sudo-capable user.
- Run everything from the repository root.
Procedure
-
Prepare the environment and verify it:
git submodule update --init --recursive ./scripts/setup.sh cp -r config.example config -
Edit
config/inventory: put the controller under[slurm-master]and compute nodes under[slurm-node](a single machine can be both). Set the connection user in[all:vars]if not root. -
Preflight — must pass before deploying:
python3 scripts/validation/deepops_doctor.py --remote --jsonFix anything in
failures(each check'sdetailsays how) and rerun. -
Deploy:
ansible-playbook -l slurm-cluster playbooks/slurm-cluster.ymlThis installs NVIDIA drivers, builds and configures Slurm, and sets up munge, NFS, and node health checks. Expect roughly 30–60 minutes on a first run.
-
Validate on a cluster node — the success signal is this, not the play recap:
python3 scripts/validation/validate_slurm.py --jsonRequire
"ok": truewithgpu_job_ok: trueandnodes_unavailable: 0.
Failure branches
- Playbook fails on a transient error (mirror timeout, apt lock,
network blip): rerun the same playbook; it is idempotent. A converged
rerun ends with
changed=0. nvidia-smiworks in the validator's srun job but "fails" over SSH: that is the login GPU-hide behavior, not an error (see AGENTS.md gotchas).gpu_job_ok: falsewith driver errors: followskills/diagnose-driver-install/.- Node shows
downordrainedinnode_states: checkscontrol show node <name>for the reason; after fixing, resume withscontrol update nodename=<name> state=resume. - Wrong or stale host facts after reprovisioning a node: rerun with
--flush-cache.
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 · 73 lines · 42 tokens per session scan A 254f68140b5f
deploy-slurm-cluster is a skill published in the GitHub repository NVIDIA/deepops (1,471 stars, last pushed today), licensed BSD-3-Clause. It adds 42 tokens to every session and 625 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).
pinggy-tunnel
Zero-install localhost tunnels over SSH via Pinggy.
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.