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/provision-with-maasWrote 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/provision-with-maas)<a href="https://agentmods.dev/skills/nvidia/deepops/provision-with-maas"><img src="https://agentmods.dev/badge/skills/nvidia/deepops/provision-with-maas/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/provision-with-maas"><img src="https://agentmods.dev/badge/skills/nvidia/deepops/provision-with-maas.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.00057 | $0.02716 |
| Opus 5.5 | $0.00023 | $0.01086 |
| Sonnet 5.5 | $0.00011 | $0.00543 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
provision-with-maas 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provision with MAAS
Keep MAAS authoritative for machine lifecycle, power, PXE/DHCP, OS images, commissioning, deployment, release, pools, zones, and tags. Use DeepOps to install a controller, request explicit deploy/tag/release operations, and turn deployed machine tags into Ansible inventory.
Preconditions
- Work from the DeepOps repository root on a prepared Ansible control machine.
- Confirm that every target is authorized for reinstallation. A deploy erases
its installed OS, and
maas_deploy.shreleases every listed deployed machine before installing it again. - Provide a MAAS 3.x controller reachable through its REST API and an OAuth1
API key in
consumer_key:token_key:token_secretformat. - Ensure the provisioning VLAN can safely use MAAS DHCP, with a reserved dynamic range that does not overlap site addresses. Targets must PXE boot on that network.
- Configure target power control in MAAS, or arrange manual power cycles.
Commission each target to
Ready, sync the requested Ubuntu image, and add an SSH public key that the operator can use after deployment. - Use Ubuntu 24.04 with the MAAS 3.7 repository for a new controller, or the MAAS 3.5 repository while the controller remains on Ubuntu 22.04.
Procedure
Prepare MAAS and DeepOps
-
Install DeepOps dependencies and create the private configuration if this checkout has not been prepared:
./scripts/setup.sh -
If DeepOps must install the MAAS controller, set
maas_adminusers,maas_dns_domain,maas_region_controller,maas_region_controller_url, andmaas_repoinconfig/group_vars/all.yml. Review the inventory, then limit the controller playbook to exactly that host:ansible-playbook -l <maas-controller-host> playbooks/provisioning/maas.ymlSkip this step when using an existing MAAS controller.
-
Edit
config/maas-inventory.yml, whichscripts/setup.shcreates fromconfig.example/maas-inventory.yml:
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 · 253 lines · 57 tokens per session scan A c3603c8fe76e
provision-with-maas is a skill published in the GitHub repository NVIDIA/deepops (1,480 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 57 tokens to every session and 2,716 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…