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
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 skills add NVIDIA/elements --skill agent-availability-reportgit clone --depth 1 https://github.com/NVIDIA/elementsWrote 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/agent-availability-report)<a href="https://agentmods.dev/skills/nvidia/elements/agent-availability-report"><img src="https://agentmods.dev/badge/skills/nvidia/elements/agent-availability-report/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/agent-availability-report"><img src="https://agentmods.dev/badge/skills/nvidia/elements/agent-availability-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00625 |
| Opus 5.5 | $0.00008 | $0.00250 |
| Sonnet 5.5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
agent-availability-report 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Availability Report
You are an Elements package availability verification agent.
Goal
Verify that the latest NVIDIA Elements packages are available on npm, confirm the Elements skill installs from GitHub, confirm the documentation site is live, and generate a brief status report.
Prepare the Run
- Read the root
AGENTS.md. - Run from the repository root with the pinned toolchain through
mise. - Preserve the current worktree. The report must not change tracked files.
Deterministic Script
Run the deterministic report script:
mise exec -- node .agents/skills/agent-availability-report/scripts/generate-availability-report.js
The script is the source of truth for:
- package order through
PACKAGES - docs URL order through
DOCS_URLS - npm metadata checks
- npm install checks
- Node package resolution checks
- Elements skill installation through the public
skillsCLI - docs URL checks
- package version comparison
- temporary project creation and cleanup
- status calculation
- report formatting
Do not repeat those lists or the report format in this skill. Update scripts/generate-availability-report.js instead.
Script Behavior
The CLI prints timestamped phase updates and 30-second heartbeats for long-running commands to standard error. Concurrent checks can finish in any order. It reserves standard output for the formatted or JSON report and exits with code 1 only when the generated report has overallStatus: "FAIL".
The exported API returns both the formatted report and structured data:
const { formattedReport, report } = await generateReport();
Return or surface formattedReport as the generated report.
The script creates temporary projects with:
mkdtemp(path.join(os.tmpdir(), 'nvidia-elements-agent-availability-report-'))npm init -ynpm install --no-audit --no-fund ...mkdtemp(path.join(os.tmpdir(), 'nvidia-elements-agent-skill-availability-'))npx [email protected] add https://github.com/nvidia/elements --skill elements- verification that
.agents/skills/elements/SKILL.mddeclares theelementsskill
What ships with it
1 file 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.
- 1mo ago Changed · +4 lines · +4 tokens per session 91c4798c2a30
- 1mo ago First seen · 78 lines · 17 tokens per session scan A 0e6b270c4e02
agent-availability-report is a skill published in the GitHub repository NVIDIA/elements (102 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 625 once invoked, about $0.0001 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
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.
react-component-design
Designs or reviews React component APIs. Handles prop drilling decisions, composition patterns, controlled/uncontrolled contracts, and minimal public API surfaces for React 18+ TypeScript components. Invoked when creating new components, refactoring existing ones, or reviewing component contracts.
beui
Pick and install beUI (@beui) animated React components through public MCP or the shadcn registry. Use when building motion UI, agent/chat interfaces, toasts, docks, bottom sheets, drawers, popovers, sliders, loaders, 404 pages, or any beui.dev component. Maps user intent to exact @beui install slugs instead of…