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/nvwb-projectnpx skills add brevdev/workshop-build-an-agent --skill nvwb-projectgit 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-project)<a href="https://agentmods.dev/skills/brevdev/workshop-build-an-agent/nvwb-project"><img src="https://agentmods.dev/badge/skills/brevdev/workshop-build-an-agent/nvwb-project.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.00045 | $0.01330 |
| Opus 5 | $0.00023 | $0.00665 |
| Sonnet 5 | $0.00009 | $0.00266 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade B, and why
nvwb-project scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Both scripts run as the `workbench` user (not root)** — any write to a system directory requires `sudo`. This includes `mkdir`, `npm install -g`, writing to `/usr/local/`, etc. Shell redirections (`>`, `>>`) also run Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Compose services are reachable by service name (e.g. `curl http://api:8080/`) via the shared `workbench` network How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NVIDIA AI Workbench — In-Container Project Awareness
This skill activates when Codex is working inside an AI Workbench project container (detected by .project/spec.yaml existing in or above the current working directory).
Detection
If .project/spec.yaml exists in the project root, this is a Workbench project. Read it first to understand the project's layout, apps, mounts, and resources.
Key Facts
- The project root is bind-mounted at
/project/inside the container - The
nvwbCLI is NOT available inside the container — allnvwbcommands must run on the user's local machine (the control plane) - This container may be running locally or on a remote — it does not matter for in-container work; the project files are always at
/project/ - Code in layout directories is live-mounted — edits take effect immediately
- The environment variable
AI_WORKBENCH_FLAG=truemay be set to detect Workbench context - Compose services are reachable by service name (e.g.
curl http://api:8080/) via the sharedworkbenchnetwork
What's Safe to Edit
Freely editable — no action needed:
- Any files in layout directories (code/, data/, models/ or custom paths from
spec.yaml) - Application code, scripts, notebooks
Requires rebuild — inform user to run nvwb build on the host:
apt.txt— system packagesrequirements.txt— pip packagespreBuild.bash— pre-install build scriptpostBuild.bash— post-install build script
Requires restart — inform user to run nvwb close then nvwb open on the host:
variables.env— runtime environment variables- Mount configuration changes in
.project/spec.yaml - App definitions in
.project/spec.yaml
Edit carefully — validate format:
.project/spec.yaml— do not break YAML structure; suggestnvwb validate project-specafter changes
When Informing the User
After editing a build-time or runtime file, always tell the user what action is needed. Examples:
I've updated
requirements.txtto add thetransformerspackage. You'll need to runnvwb buildon the host to rebuild the container with this change.
What ships with it
12 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.
- hooks/cursor-inner-files.sh 1.9 KB runs code
- hooks/cursor-inner-read.sh 782 B runs code
- hooks/cursor-inner-shell.sh 1.5 KB runs code
- hooks/inner-agent-bash.sh 1.7 KB runs code
- hooks/inner-agent-files.sh 1.9 KB runs code
- hooks/inner-agent-read.sh 793 B runs code
- hooks/outer-agent-bash.sh 2.0 KB runs code
- hooks/outer-agent-files.sh 914 B runs code
- hooks/sensitive-patterns.sh 3.8 KB runs code
- hooks/test-hooks.sh 14 KB runs code
- references/agent-bridge.md 14 KB
- references/config-files.md 5.9 KB
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 · 94 lines · 45 tokens per session scan B 323f4b4d0a5b
nvwb-project is a skill published in the GitHub repository brevdev/workshop-build-an-agent (133 stars, last pushed 17d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,330 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…