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 audit-accessibilitygit 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/audit-accessibility)<a href="https://agentmods.dev/skills/nvidia/elements/audit-accessibility"><img src="https://agentmods.dev/badge/skills/nvidia/elements/audit-accessibility/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/audit-accessibility"><img src="https://agentmods.dev/badge/skills/nvidia/elements/audit-accessibility.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.00098 | $0.00701 |
| Opus 5.5 | $0.00039 | $0.00280 |
| Sonnet 5.5 | $0.00020 | $0.00140 |
| Haiku 4.5 | $0.00010 | $0.00070 |
Grade A, and why
audit-accessibility 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditing
You MUST read projects/site/src/docs/internal/guidelines/testing-accessibility.md before proceeding.
Audit Scope
When the user invokes this skill for a component, perform the following layers of accessibility verification:
1. Static analysis (ESLint lit-a11y)
Run ESLint on the component source and check for lit-a11y rule violations:
cd projects/core && pnpm exec eslint --no-warn-ignored src/<component>/<component>.ts
Review the component template for common issues:
- Missing
aria-labeloraria-labelledbyon interactive elements - Missing
roleattributes on custom interactive patterns - Images without
alttext - Form inputs without associated labels
2. Runtime testing (axe-core)
Verify <component>.test.axe.ts exists and covers all component variants:
Read path="projects/core/src/<component>/<component>.test.axe.ts"
Check that the test:
- Imports
runAxefrom@internals/testing/axe - Tests every applicable status and size variant, plus the
disabledstate when the component supports it - Expects zero violations:
expect(results.violations.length).toBe(0) - Properly creates and removes fixtures
3. ARIA pattern verification
Identify which WAI-ARIA Authoring Practices pattern the component implements. Verify:
- Correct
roleattribute on the host or internal elements - Required ARIA states (
aria-expanded,aria-selected,aria-checked, etc.) - Proper
tabindexmanagement - Focus management for composite widgets
4. Keyboard navigation
Check if the component uses the keynav reactive controller from @nvidia-elements/core/internal:
Grep pattern="keynav|keyNavigationList|KeyNav" path="projects/core/src/<component>/"
Verify keyboard interactions match the ARIA pattern:
- Arrow keys for navigation within composite widgets
- Enter/Space for activation
- Escape for dismissal
- Tab for focus entry/exit
- Home/End for first/last item
5. Color contrast (theme tokens)
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 · 88 lines · 98 tokens per session scan A 00e2ecd79cd3
audit-accessibility is a skill published in the GitHub repository NVIDIA/elements (102 stars, last pushed today), licensed Apache-2.0. It adds 98 tokens to every session and 701 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
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.
Cypress v14 Component Testing
Component testing patterns with Cypress v14 including React, Vue, and Angular component mounting, custom mount commands, interaction testing, visual snapshots, and integration with Vite and Webpack bundlers.
igniteui-blazor-generate-from-image-design
Implement Blazor application views from design images using Ignite UI Blazor components. Uses MCP servers (igniteui-cli, igniteui-theming) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working…
igniteui-wc-generate-from-image-design
Implement application views from design images using Ignite UI Web Components. Uses MCP servers (igniteui-cli, igniteui-theming) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working view with…
igniteui-angular-generate-from-image-design
Implement Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built…
igniteui-blazor-components
Covers non-grid Ignite UI for Blazor UI components: application setup, form controls (inputs, combos, selects, date/time pickers, calendar, checkbox, radio, switch, slider, rating), layout containers (tabs, stepper, accordion, expansion panel, navigation drawer, navbar, tree), data-display components (list, card…