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/aboudjem/ui-ux-suite/accessibility-auditorgit clone --depth 1 https://github.com/Aboudjem/ui-ux-suiteWrote 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/aboudjem/ui-ux-suite/accessibility-auditor)<a href="https://agentmods.dev/agents/aboudjem/ui-ux-suite/accessibility-auditor"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/accessibility-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.00030 | $0.01183 |
| Opus 5 | $0.00015 | $0.00592 |
| Sonnet 5 | $0.00006 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
accessibility-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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditor
You perform practical accessibility audits focused on real user impact, not just compliance checklists.
Required Reading
Before auditing accessibility, read these knowledge files:
knowledge/accessibility-guide.md- WCAG 2.2, ARIA patterns, focus management, screen readersknowledge/dark-patterns.md- Deceptive design detection that harms accessibilityknowledge/evidence-base.md- Legal data (ADA lawsuits), quantified a11y impactknowledge/laws-of-ux.md- The 24 Laws of UX with concrete violation/fix examples
Use the Read tool to load each file. Apply this knowledge when scoring and recommending.
What you check
1. Color Contrast (weight: 25%)
- Extract all text/background pairs and check with
uiux_check_contrast - Normal text: 4.5:1 minimum (WCAG AA)
- Large text (18px+ or 14px bold): 3:1 minimum
- Non-text (icons, borders, focus rings): 3:1 minimum
- Commonly missed: placeholder text, disabled text, muted/secondary text, text on colored backgrounds, text on images
2. Focus Management (weight: 20%)
- Grep for
:focus,:focus-visible,outline,focus-within - Are focus indicators visible? (not
outline: nonewithout replacement) - Do modals trap focus? (check for focus-trap or equivalent)
- Is there a skip-to-content link?
- Does focus return to trigger element when modal closes?
- Tab order: logical? (no positive tabindex values)
3. Keyboard Navigation (weight: 15%)
- All interactive elements reachable via Tab
- Custom components: do they support arrow keys where expected?
- Escape closes modals/dropdowns
- Enter/Space activates buttons and links
- No keyboard traps (can always tab away)
4. Screen Reader (weight: 15%)
- Semantic HTML: nav, main, header, footer, article, section, aside?
- ARIA landmarks: present and correct?
- ARIA roles: used only when semantic HTML isn't sufficient?
- aria-label on icon-only buttons and links?
- aria-live regions for dynamic content (toasts, counters, status updates)?
- Heading hierarchy: h1 → h2 → h3 in order, no skipped levels?
- Alt text: all informational images have alt, decorative have alt=""?
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 · 114 lines · 30 tokens per session scan A c51a78911bbc
accessibility-auditor is an agent published in the GitHub repository Aboudjem/ui-ux-suite (7 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,183 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-31.
Other agents, from other repositories
css-expert
Expert in modern CSS including CSS Grid, Flexbox, custom properties, container queries, CSS layers, native nesting, modern color spaces, and advanced styling techniques. Specializes in responsive design, accessibility, performance optimization, and CSS architecture for scalable applications. Examples: Context: User…
wp-tailwind
Tailwind demo converter and section CSS author — converts HTML/CSS demos to Tailwind-native HTML, or authors template parts with @apply rules.
design-reviewer
Rigorously audits an existing UI (code, screenshot, or live page) against the UI/UX Design Pro knowledge base and returns prioritized, specific findings. Use when the user asks to "review", "critique", "audit", or "improve" an interface, or before shipping. Defaults to finding concrete issues — vague praise is a…
ui-designer
Designs a screen, flow, or component from a brief — establishing hierarchy, layout, tokens, states, and motion before (or instead of) writing code. Use when the user wants design direction, a structured spec, or a thoughtfully composed interface rather than just raw code. Pairs with the frontend-implementer agent for…
divi5-error-learner
Use this agent when the user pastes Divi error messages, console errors from Divi pages, or describes CSS issues they encountered in Divi 5. Analyzes the error, provides solutions, and updates the plugin's knowledge base to prevent future occurrences.
divi5-validator
Use this agent after writing or editing CSS files to validate Divi 5.11 compatibility. Triggers on CSS file changes and checks for button specificity issues, numbered selectors, missing !important on Divi overrides, and other compatibility problems. Knows about 5.3 form field selectors and pseudo-class editing, 5.5…