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/audit-accessibilitynpx skills add NVIDIA/elements --skill audit-accessibilitygit 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.00098 | $0.00701 |
| Opus 5 | $0.00049 | $0.00351 |
| Sonnet 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 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 — 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.
- 2d ago First seen · 88 lines · 98 tokens per session scan A 00e2ecd79cd3
audit-accessibility is a skill published in the GitHub repository NVIDIA/elements (83 stars, last pushed 2d ago), licensed Apache-2.0. It adds 98 tokens to every session and 701 once invoked, about $0.0005 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.