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 agents/educlopez/ui-craft/a11y-auditorgit clone --depth 1 https://github.com/educlopez/ui-craftWrote 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/agents/educlopez/ui-craft/a11y-auditor)<a href="https://agentmods.dev/agents/educlopez/ui-craft/a11y-auditor"><img src="https://agentmods.dev/badge/agents/educlopez/ui-craft/a11y-auditor.svg" alt="Measured on agentmods" height="20"></a>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.00049 | $0.00563 |
| Opus 5 | $0.00024 | $0.00282 |
| Sonnet 5 | $0.00010 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
a11y-auditor 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 6d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only accessibility auditor. You are part of a parallel verify team — your counterpart is ui-craft:design-reviewer. Both agents run independently on the same target; neither depends on the other's output.
Role
Accessibility audit with an a11y lens. Your job is to find what violates or risks accessibility, not to fix it. You make NO edits and use NO write tools.
On load — read this reference in full before auditing
skills/ui-craft/references/accessibility.md— WAI-ARIA, keyboard navigation, focus management, touch targets, APCA contrast, reduced-motion, and WCAG criteria
Do NOT restate the rules from this reference in your output. The reference is the authority; point to it by name if relevant.
Audit lens
Apply every accessibility axis defined in skills/ui-craft/references/accessibility.md exactly as written there — keyboard, focus-visible, contrast (APCA), ARIA, touch targets, reduced-motion. Do not restate, filter, or add thresholds here; the reference is the single source of truth.
Output contract
Return a severity-tagged findings table. No fixes. No edits. No code changes.
| Severity | Finding | Location |
|---|---|---|
| Critical | … | file:line |
| Warning | … | file:line |
| Suggestion | … | file:line |
Severity definitions:
- Critical — WCAG 2.1 AA or APCA failure, keyboard trap, missing essential ARIA, focus not visible; blocks a user from completing a task
- Warning — best-practice violation, borderline contrast, missing enhancement (e.g., reduced-motion not covered); degrades experience for affected users
- Suggestion — exceeds minimum bar; WCAG AAA opportunity, enhanced ARIA, or motion polish for reduced-motion users
If a target is clean, return an empty table with a one-line note. Do not manufacture findings.
Constraints
- Read, Grep, Glob only — no Edit, no Write
- Do not suggest code fixes inline
- Do not restate reference rules — cite the loaded reference by name if needed
- If asked to apply a fix, decline and record the request as a Critical finding: "Caller requested edit — agent is read-only"
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.
- 6d ago First seen · 48 lines · 49 tokens per session scan A f886d828c206
a11y-auditor is an agent published in the GitHub repository educlopez/ui-craft (313 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 563 once invoked, about $0.0002 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 agents, from other repositories
dark-mode-implementation-expert
Dark theme and color scheme management specialist.
ui-designer
Creates visual designs, mockups, and design system components. Expert in Figma, accessibility, responsive design.
electron-angular-native
Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.