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 guidance-api-designgit 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/guidance-api-design)<a href="https://agentmods.dev/skills/nvidia/elements/guidance-api-design"><img src="https://agentmods.dev/badge/skills/nvidia/elements/guidance-api-design/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-api-design"><img src="https://agentmods.dev/badge/skills/nvidia/elements/guidance-api-design.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.00103 | $0.00461 |
| Opus 5.5 | $0.00041 | $0.00184 |
| Sonnet 5.5 | $0.00021 | $0.00092 |
| Haiku 4.5 | $0.00010 | $0.00046 |
Grade A, and why
guidance-api-design 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.
What it actually says
Guidance API Design
You MUST review the relevant API design guidelines before designing or modifying component APIs.
When to Use This Skill
- Designing properties and attributes for new components
- Creating CSS custom properties for theming
- Avoiding impossible states in component APIs
- Choosing between properties, attributes, and slots
- Designing custom events
- Planning component composition patterns
- Setting up package exports and dependencies
Stateless Components
When creating new components or features that may contain user state review the Stateless Components Guidelines.
Properties vs Attributes
When working with JavaScript properties and HTML attributes review the Properties & Attributes Guidelines.
Styles & CSS Custom Properties
When working with CSS, CSS Custom Properties or Design Tokens review the Styles & CSS Custom Properties Guidelines.
Component Composition
When creating a new API or determining API design of parent child relationships between components review the Component Composition Guidelines.
Slots
When working with user provided content or container-like components review the Slots Guidelines.
Custom Events
When creating new events or listening to existing event review the Custom Events Guidelines.
Component Registration
When creating new components or using components as dependencies review the Component Registration Guidelines.
Packaging & Exports
When creating a new component or package review the Packaging & Exports Guidelines.
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 · 51 lines · 103 tokens per session scan A 1620c0574a31
guidance-api-design is a skill published in the GitHub repository NVIDIA/elements (102 stars, last pushed today), licensed Apache-2.0. It adds 103 tokens to every session and 461 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
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…
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.
igniteui-wc-choose-components
Identify and select the right Ignite UI Web Components for your app UI, then navigate to official docs, usage examples, and API references.
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.
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.