NVIDIA Elements is a design system and agent-oriented toolkit for building operational interfaces for AI/ML, robotics, and autonomous-vehicle software. Its CLI and MCP tools provide component APIs, design tokens, examples, imports, validation, and setup guidance across several web frameworks.
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/elementsnpx agentmods add skills/nvidia/elements/guidance-build-systemWrote 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/elements/guidance-build-system)<a href="https://agentmods.dev/skills/nvidia/elements/guidance-build-system"><img src="https://agentmods.dev/badge/skills/nvidia/elements/guidance-build-system/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/elements/guidance-build-system"><img src="https://agentmods.dev/badge/skills/nvidia/elements/guidance-build-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 34 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 50 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00101 | $0.00873 |
| Opus 5.5 | $0.00040 | $0.00349 |
| Sonnet 5.5 | $0.00020 | $0.00175 |
| Haiku 4.5 | $0.00010 | $0.00087 |
Grade A, and why
guidance-build 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidance Build System
You MUST review the build system documentation before modifying build configurations or troubleshooting build issues.
When to Use This Skill
- Optimizing build performance and parallelization
- Understanding Wireit task dependencies
- Troubleshooting build failures or cache issues
- Adding new build tasks to projects
- Configuring build orchestration across packages
- Understanding CI/CD build pipeline
Quick Reference
Common Commands
# Full CI locally (lint, build, test):same as CI pipeline
pnpm run ci
# Clean everything (node_modules, dist, .wireit caches)
pnpm run ci:reset
# Build a single project
cd projects/core && pnpm run build
# Force that project's Wireit scripts to rerun
mise exec -- git clean -dfX -- .wireit
mise exec -- pnpm run build
# Dev mode with watch
cd projects/core && pnpm run dev
Wireit Basics
Wireit configs live in each project's package.json under the wireit key. Each task declares:
command:the shell command to rundependencies:other wireit tasks that must complete first (can be cross-package)files:input file globs for cache invalidationoutput:output file globs that get cached
Wireit skips tasks whose inputs have not changed since the last run. WIREIT_CACHE=none turns off output caching but does not bypass this incremental freshness check. To force a rerun, run mise exec -- git clean -dfX -- .wireit from the target project directory before invoking the project script.
Dependency Patterns
Cross-package dependencies use the <package>:<script> format:
{
"wireit": {
"build": {
"dependencies": ["../themes:build", "../styles:build"],
"command": "vite build",
"files": ["src/**/*", "tsconfig.json"],
"output": ["dist/**"]
}
}
}
Troubleshooting Build Failures
| Symptom | Fix |
|---|---|
| Stale cache causing wrong output | Clean .wireit/ in the affected project, then rebuild |
| "Cannot find module" after package changes | Run pnpm i --frozen-lockfile to re-link workspaces |
| TypeScript errors after dependency update | Rebuild dependencies first: cd projects/themes && pnpm run build |
| CI passes locally but fails in pipeline | Check Node version (node -v should match .nvmrc) and pnpm version |
| Full reset | pnpm run ci:reset && pnpm i --frozen-lockfile && pnpm run ci |
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 · 98 lines · 101 tokens per session scan A e9cfafef407f
guidance-build is a skill published in the GitHub repository NVIDIA/elements (102 stars, last pushed today), licensed Apache-2.0. It adds 101 tokens to every session and 873 once invoked, about $0.0004 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
angular
Use when building, refactoring, or debugging Angular (v20/21+): standalone components, signals, zoneless change detection, @if/@for/@defer control flow, inject() DI, resource()/httpResource(), RxJS interop, NgRx SignalStore, ng CLI. NOT React (that is react), NOT Next.js (that is nextjs), NOT a TypeScript language…
module-federation
Add, review, or debug client-rendered Module Federation support in Rsbuild-first TypeScript applications. Covers host/remote roles, exposes, remotes, shared dependencies, generated types, runtime loading failures, and observability checks.
vue-application-structure
Establishes or reviews the directory layout, component conventions, composable design, Pinia store structure, and Vue Router configuration for a Vue 3 TypeScript application. Invoked when the user asks to structure a Vue app, set up the project layout, or review Vue architecture.
react-application-structure
Establishes or reviews the directory layout, feature boundaries, state design, routing approach, and data-fetching conventions for a React 18+ TypeScript application. Invoked when the user asks to structure a React app, set up a scalable architecture, or review React project organization.
vue-component-design
Designs or reviews Vue 3 component APIs. Handles prop drilling decisions, applies compound component patterns with provide/inject, defines minimal public API surfaces with typed props/emits/slots, and enforces Vue 3.4+ composition conventions. Invoked when creating new components, refactoring existing ones, or…
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.