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 authoring-testsgit 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/authoring-tests)<a href="https://agentmods.dev/skills/nvidia/elements/authoring-tests"><img src="https://agentmods.dev/badge/skills/nvidia/elements/authoring-tests/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/authoring-tests"><img src="https://agentmods.dev/badge/skills/nvidia/elements/authoring-tests.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.00113 | $0.00707 |
| Opus 5.5 | $0.00045 | $0.00283 |
| Sonnet 5.5 | $0.00023 | $0.00141 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade A, and why
authoring-tests 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Tests
You MUST review @projects/site/src/docs/internal/guidelines/testing.md before making any testing changes.
When to Use This Skill
- Creating new test files for components (
.test.ts,.test.axe.ts,.test.visual.ts,.test.ssr.ts,.test.lighthouse.ts) - Debugging test failures or updating existing tests
- Understanding testing utilities from
@internals/testing - Setting up test configurations or HTML templates
- Writing tests that follow project patterns
Test Type Guidelines
Read the specific guideline based on the test type you're working with:
- Unit Tests (
.test.ts): Read testing-unit.md - coverscreateFixture,elementIsStable, event testing - Accessibility Tests (
.test.axe.ts): Read testing-accessibility.md - covers axe-core usage, WCAG compliance - Visual Tests (
.test.visual.ts): Read testing-visual.md - covers Playwright screenshots, theme testing - SSR Tests (
.test.ssr.ts): Read testing-ssr.md - covers server-side rendering compatibility - Lighthouse Tests (
.test.lighthouse.ts): Read testing-lighthouse.md - covers performance, accessibility scores
Key Principles
- Test Isolation: Each test should be independent with proper setup/teardown using
createFixtureandremoveFixture - Wait for Stability: Always use
elementIsStable()before making assertions on Lit components - Comprehensive Coverage: All new components require unit, accessibility, and visual tests at minimum
- Real User Events: Use
emulateClickanduntilEventfor realistic event testing - Theme Testing: Visual tests should cover both light and dark themes
References
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 · 45 lines · 113 tokens per session scan A 2219ae60c16f
authoring-tests is a skill published in the GitHub repository NVIDIA/elements (102 stars, last pushed today), licensed Apache-2.0. It adds 113 tokens to every session and 707 once invoked, about $0.0005 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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
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.
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…
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…