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/brevdev/workshop-build-an-agent/nvwbnpx skills add brevdev/workshop-build-an-agent --skill nvwbgit clone --depth 1 https://github.com/brevdev/workshop-build-an-agentWrote 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/brevdev/workshop-build-an-agent/nvwb)<a href="https://agentmods.dev/skills/brevdev/workshop-build-an-agent/nvwb"><img src="https://agentmods.dev/badge/skills/brevdev/workshop-build-an-agent/nvwb.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00052 | $0.01044 |
| Opus 5 | $0.00026 | $0.00522 |
| Sonnet 5 | $0.00010 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
nvwb 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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NVIDIA AI Workbench — Local Machine (Control Plane)
NVIDIA AI Workbench is a lightweight, containerized development platform for GPU-accelerated AI/ML workflows. Every project is a Git repo with a .project/spec.yaml that defines the container environment. It supports Docker and Podman as container runtimes.
The nvwb CLI always runs on the local machine — the user's laptop or desktop. From there it manages contexts, which may be local (container on the same machine) or remote (container on a server or cloud instance accessed via SSH). Codex using this skill is on the local machine.
The user wants help with: $ARGUMENTS
Core Concepts
- Contexts — Locations/machines where projects run (local, remote SSH, Brev cloud)
- Projects — Git repos with container configuration (
.project/spec.yaml) - Applications — Services inside the container (JupyterLab, VS Code, custom webapps/processes)
- Environment Variables — Runtime values set via CLI; sensitive ones (
--is-sensitive) are masked in output. Values are never committed to Git. Projects may declare required secret variable names inspec.yamlunderexecution.secrets.
Current State Detection
Before taking action, check the current state:
nvwb list contexts # What locations are configured?
nvwb status # Is a project open? Is the container running?
nvwb list projects # What projects exist in the active context?
Build vs Runtime Isolation
Build-time (changes require nvwb build):
apt.txt— system packagesrequirements.txt— pip packagespreBuild.bash/postBuild.bash— custom build scripts- Package manager entries in
spec.yaml
Runtime (changes require container restart: nvwb close + nvwb open):
variables.env— environment variables- Mount configuration changes
- App definitions in
spec.yaml
No action needed:
- Code in layout directories (code/, data/, models/) — live-mounted at
/project/
Key Environment Variables
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 91 lines · 52 tokens per session scan A 84251a1067d9
nvwb is a skill published in the GitHub repository brevdev/workshop-build-an-agent (133 stars, last pushed 16d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,044 once invoked, about $0.0003 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
release-rome-image
Release a new Rome runtime image by pushing a vX.Y.Z tag — pick the version, verify main is releasable, push the tag, and confirm the image published to Docker Hub. Covers the v runtime-image tag only, not the desktop app (desktop-v) and not npm packages (ui-v, app-runtime-v).