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 AmadeusITGroup/otter --skill a11y-component-auditgit clone --depth 1 https://github.com/AmadeusITGroup/otterWrote 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/amadeusitgroup/otter/a11y-component-audit)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/a11y-component-audit"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-component-audit/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/amadeusitgroup/otter/a11y-component-audit"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-component-audit.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.00040 | $0.00788 |
| Opus 5.5 | $0.00016 | $0.00315 |
| Sonnet 5.5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
a11y-component-audit 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Component Accessibility Audit
Compliance Target
WCAG 2.1 AA for existing components. WCAG 2.2 AA for newly created components. Accessibility is a release gate, not a follow-up.
<hard_rules>
- Apply [[a11y-aria-patterns]] for accessible names, keyboard behavior, focus outlines, and validation ARIA.
- Form controls: programmatic label (
<label for="[id]">oraria-labelledby). Placeholder is NOT a label. - No color-only information: status, error, and category indicators carry text or icon in addition to color.
- Contrast: text 4.5:1 (3:1 for large text ≥18px or ≥14px bold), UI components and focus indicators 3:1. Use design tokens — no raw hex values.
- Reduced motion: animations longer than 200 ms must respect
prefers-reduced-motion: reduce. - No tooltip on disabled controls: use a visible sibling message with
aria-describedbyinstead. - Images and icons: decorative images use
alt=""oraria-hidden="true"; informative images have descriptivealttext; functional images describe their purpose, not appearance; never prefix with "image of" or "icon of". </hard_rules>
Axe test coverage — verify an axe test exists for the component (follow [[a11y-axe-playwright]] for conventions). If none exists, record as a finding. Record: covered or missing — no axe test found.
Keyboard pass — follow [[a11y-keyboard-playwright]] for patterns and helpers. Record: verified or findings list.
ARIA pattern validation — validate each changed component against [[a11y-aria-patterns]]. Do NOT improvise ARIA roles. Record: named pattern(s) or finding with proposed pattern.
Contrast verification
Confirm all colors use design tokens (no raw hex). Run token contrast linter if available. Record: verified via tokens or findings list.
Reduced motion check
Confirm every animation > 200 ms has a prefers-reduced-motion: reduce rule. Record: respected or n/a — no animations.
Disabled controls (only if the component includes disabled form controls)
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 · 69 lines · 40 tokens per session scan A 6acad6f5f175
a11y-component-audit is a skill published in the GitHub repository AmadeusITGroup/otter (59 stars, last pushed today), licensed BSD-3-Clause. It adds 40 tokens to every session and 788 once invoked, about $0.0002 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
elements
Use this skill by default for any UI-related work or with NVIDIA Elements (nve-), including creating, editing, reviewing, or debugging HTML, CSS, layout, theming, components, applications, prototypes, Claude Artifacts, Codex Sites pages, and standalone UI artifacts.
authoring-patterns
Convert validated playground templates or HTML compositions into reusable pattern files (.examples.ts) in the pattern library. Use this skill whenever the user wants to save, persist, store, or catalog a template, prototype, composition, or playground result as a reusable pattern. Trigger on phrases like "save as…
audit-accessibility
Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit…
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…
igniteui-angular-figma-to-app
Builds Angular views from Figma designs with Ignite UI for Angular, supporting Indigo.Design kits, third-party kits, and plain frames. Uses Figma, Ignite UI CLI, theming, and Playwright MCP servers. WHEN TO USE: implementing a Figma design or artboard in an Ignite UI Angular project. WHEN NOT TO USE: screenshots or…
igniteui-angular-generate-from-image-design
Implements 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. WHEN TO USE: the user provides a design image (screenshot, mockup, wireframe) and wants it built…