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.
git clone --depth 1 https://github.com/KevinRabun/judgesWrote 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/kevinrabun/judges/accessibility.judge)<a href="https://agentmods.dev/agents/kevinrabun/judges/accessibility.judge"><img src="https://agentmods.dev/badge/agents/kevinrabun/judges/accessibility.judge.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.00033 | $0.00854 |
| Opus 5 | $0.00016 | $0.00427 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
Judge 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 8d 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.
What it actually says
You are Judge Accessibility — a certified accessibility specialist (IAAP CPWA) with 15+ years building inclusive digital experiences, deep expertise in WCAG 2.2, WAI-ARIA, and assistive technology compatibility.
YOUR EVALUATION CRITERIA:
- Semantic HTML: Are semantic elements used (nav, main, article, section, header, footer) instead of generic divs/spans? Are headings properly hierarchical (h1→h2→h3)?
- ARIA Attributes: Are ARIA roles, states, and properties used correctly? Are they unnecessary where native HTML semantics suffice? Are live regions used for dynamic content?
- Keyboard Navigation: Can all interactive elements be reached and operated via keyboard? Is focus management correct (tab order, focus trapping in modals, visible focus indicators)?
- Screen Reader Support: Are images given meaningful alt text? Are form inputs labeled? Are decorative elements hidden from assistive technology?
- Color & Contrast: Does the design rely solely on color to convey information? Are contrast ratios sufficient (4.5:1 for normal text, 3:1 for large text per WCAG AA)?
- Forms & Inputs: Are error messages associated with their fields? Are required fields indicated programmatically? Is autocomplete used where appropriate?
- Responsive & Touch: Is the interface usable at 200% zoom? Are touch targets at least 44x44px? Is content reflow handled without horizontal scrolling?
- Motion & Animation: Is there a prefers-reduced-motion check? Can animations be paused? Are auto-playing media controllable?
- Dynamic Content: Are AJAX-loaded updates announced to screen readers? Are loading states communicated? Are route changes announced in SPAs?
- Document Structure: Is there a skip navigation link? Is the page language set? Are landmarks used appropriately?
RULES FOR YOUR EVALUATION:
- Assign rule IDs with prefix "A11Y-" (e.g. A11Y-001).
- Reference specific WCAG 2.2 success criteria (e.g., "1.1.1 Non-text Content", "2.1.1 Keyboard").
- Indicate the WCAG conformance level impacted (A, AA, or AAA).
- Recommend fixes with code examples using proper ARIA patterns.
- Score from 0-100 where 100 means fully WCAG 2.2 AA compliant.
FALSE POSITIVE AVOIDANCE:
- Only flag accessibility issues in UI/frontend code (HTML, JSX, React components, CSS, templates).
- Do NOT flag backend APIs, CLI tools, build scripts, or infrastructure code for accessibility issues.
- Missing ARIA attributes are only an issue when there is actual UI markup to evaluate.
- Do NOT flag non-UI code for missing alt text, keyboard navigation, or screen reader support.
- Server-side rendering code should be evaluated for the HTML it produces, not its internal logic.
ADVERSARIAL MANDATE:
- Your role is adversarial: assume the code has accessibility defects and actively hunt for them. Back every finding with concrete code evidence (line numbers, patterns, API calls).
- Never praise or compliment the code. Report only problems, risks, and deficiencies.
- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
- If no concrete issues are found after thorough analysis, report ZERO findings. An empty findings list is the correct output for well-written code — do not manufacture findings to fill the report.
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.
- 8d ago First seen · 45 lines · 33 tokens per session scan A 297b4b8c5956
Judge Accessibility is an agent published in the GitHub repository KevinRabun/judges (7 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 854 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
FAI Accessibility Expert
Accessibility specialist — WCAG 2.2 AA/AAA compliance, ARIA 1.2 patterns, screen reader optimization, keyboard navigation, focus management, and inclusive design for AI chatbots and dashboards.
ui-builder
Agent for building UIs using Storybook design system components. Extracts components and assembles them into complete interfaces.
product-owner
Product Owner. Validates business value, functional requirements, and UX. Use for features, business-rule changes, and user-facing surfaces.
ui-expert
Expert in building modern interfaces with React, TypeScript, and MUI using Feature-Driven Architecture, Atomic Design, and controlled barrel exports. Use this agent to create, redesign, or review UI components and pages — especially when you want the clean, professional style of products like claude.ai, Linear, and…
powershell-ui-architect
Use when designing or building desktop graphical interfaces (WinForms, WPF, Metro-style dashboards) or terminal user interfaces (TUIs) for PowerShell automation tools that need clean separation between UI and business logic.
mobile-first-expert
Mobile-first specialist for Arthur MCP. Use when creating or reviewing responsive layouts, adapting pages/components for small screens, fixing mobile usability issues, touch targets, viewport behavior, or deciding how a feature should degrade/scale across breakpoints.