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 agentmods add skills/nvidia/elements/authoring-testsnpx skills add NVIDIA/elements --skill authoring-testsgit clone --depth 1 https://github.com/NVIDIA/elementsWhat 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 | $0.00113 | $0.00707 |
| Opus 5 | $0.00056 | $0.00353 |
| Sonnet 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 2d 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.
- 2d ago First seen · 45 lines · 113 tokens per session scan A 2219ae60c16f
authoring-tests is a skill published in the GitHub repository NVIDIA/elements (83 stars, last pushed 2d ago), licensed Apache-2.0. It adds 113 tokens to every session and 707 once invoked, about $0.0006 per session on Opus 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
design-doc-interviewer
Interview the user to turn a proposed product/engineering change into a structured design document. Use when the user asks to be interviewed, wants help clarifying a design, or wants a design doc produced from Q&A. Emphasize numbered questions (few at a time), capture requirements/constraints/UX/data/logic/testing…
ideate
Capture and document a new idea in this repo. Use when the user says things like "help me brainstorm", "I have an idea", or "let's capture this for the future" and wants it recorded in design/ideas/ with a summary, supporting research (repo context + web if useful), and a sketch.
beui
Pick and install beUI (@beui) animated React components from 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 inventing custom…
beui-pro
Choose, inspect, install, and compose licensed beUI Pro premium React blocks from the authenticated shadcn registry. Use when building or improving landing pages with beUI Pro, installing @beui-pro items, selecting premium heroes, features, pricing, social proof, CTAs, navigation, footers, or other page sections, or…
ui-development
Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS. TRIGGER when user asks to "create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI", runs foundry ui pages create or foundry ui run, or needs help with Vite…
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.