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 instructions/nvidia/deepops/agents-mdgit 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.01353 | $0.01353 |
| Opus 5 | $0.00677 | $0.00677 |
| Sonnet 5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
deepops AGENTS.md 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepOps agent operating guide
This file is the entry point for AI agents (and new humans) operating this repository. DeepOps deploys and manages GPU clusters — Slurm or Kubernetes on NVIDIA GPU servers — using Ansible. Everything here is driven by playbooks against an inventory you control; there is no server component.
Load only what the task needs: this file for orientation and the golden
paths, docs/ for depth, skills/ for step-by-step procedures with failure
handling.
Repository map
| Path | Purpose |
|---|---|
playbooks/ |
Entry points. slurm-cluster.yml and k8s-cluster.yml are the two top-level cluster deploys; subdirectories hold component playbooks. |
roles/ |
Ansible roles (NVIDIA drivers, container toolkit, DGX software, monitoring, Slurm, storage). |
config.example/ |
Template configuration. Copy to config/ and edit; never edit config.example/ for a deployment. |
config/ |
Your site configuration and inventory (git-ignored; created by you). |
scripts/validation/ |
Machine-readable preflight and post-deploy validation. Start here to know if anything worked. |
scripts/ |
Setup and helper scripts (setup.sh installs Ansible and dependencies). |
submodules/kubespray |
Kubernetes deployment engine. Must be initialized before Kubernetes work. |
docs/ |
Topic documentation: deepops/, slurm-cluster/, k8s-cluster/, container/, airgap/. |
skills/ |
Reusable agent procedures with preconditions, commands, expected output, and failure branches. |
First-time setup (once per provisioning machine)
git submodule update --init --recursive
./scripts/setup.sh # installs Ansible + Galaxy dependencies
cp -r config.example config # then edit config/inventory
python3 scripts/validation/deepops_doctor.py --json # verify before deploying
The doctor must report "ok": true (or you must understand every failure)
before you run any cluster playbook. With --remote it also proves SSH
reachability to every inventory host.
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 · 108 lines · 1,353 tokens per session scan A 40cc2998514d
deepops AGENTS.md is an instructions file published in the GitHub repository NVIDIA/deepops (1,469 stars, last pushed 5d ago), licensed BSD-3-Clause. It adds 1,353 tokens to every session, about $0.0068 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.