workshop-build-an-agent: Skill for Claude Code

.agents/skills/nvwb-project/SKILL.md

nvwb-project is a skill for Claude Code from brevdev/workshop-build-an-agent. It costs 45 tokens per session (1,330 once invoked), scanned B, original, Apache-2.0.

A guide for working inside an NVIDIA AI Workbench project container, identified by a .project/spec.yaml file. It explains the project layout and how edits, services, and environment changes behave there.

In plain words
What is it for?
It helps inspect the project specification, edit live-mounted code, reach services by name, and understand when environment changes require a rebuild or restart.
Why use it?
It prevents confusion about where files live and which operations must happen inside or outside the container.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is brevdev/workshop-build-an-agent's own configuration. It tells Claude Code how to work on workshop-build-an-agent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything workshop-build-an-agent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to brevdev/workshop-build-an-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/brevdev/workshop-build-an-agent/main/.agents/skills/nvwb-project/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/brevdev/workshop-build-an-agent

Made for: Claude Code.

Wrote 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.

agentmods badge for nvwb-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/brevdev/workshop-build-an-agent/nvwb-project/github.svg)](https://agentmods.dev/skills/brevdev/workshop-build-an-agent/nvwb-project)
Your own site
<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/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.

agentmods 80×15 button for nvwb-project

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,330 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.01330
Opus 5.5 $0.00018 $0.00532
Sonnet 5.5 $0.00009 $0.00266
Haiku 4.5 $0.00005 $0.00133

Measured 1mo ago against content hash 323f4b4d0a5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo ago.

The scan reads SKILL.md. This mod also ships 10 executable files (hooks/cursor-inner-files.sh, hooks/cursor-inner-read.sh, hooks/cursor-inner-shell.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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
.agents/skills/nvwb-project/SKILL.md · 94 lines

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 nvwb CLI is NOT available inside the container — all nvwb commands 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=true may be set to detect Workbench context
  • Compose services are reachable by service name (e.g. curl http://api:8080/) via the shared workbench network

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 packages
  • requirements.txt — pip packages
  • preBuild.bash — pre-install build script
  • postBuild.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; suggest nvwb validate project-spec after 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.txt to add the transformers package. You'll need to run nvwb build on the host to rebuild the container with this change.

Read the full file on GitHub · 94 lines

Changes

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.

  1. 1mo ago First seen · 94 lines · 45 tokens per session scan B 323f4b4d0a5b

Subscribe to this mod's changes

nvwb-project is a skill published in the GitHub repository brevdev/workshop-build-an-agent (151 stars, last pushed 16d 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.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.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens