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/yassinello/claude-plugin-prd-workflow/accessibility-auditorgit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/yassinello/claude-plugin-prd-workflow/accessibility-auditor)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/accessibility-auditor"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/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.00022 | $0.01065 |
| Opus 5 | $0.00011 | $0.00532 |
| Sonnet 5 | $0.00004 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00106 |
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditor Agent
WCAG 2.1 compliance expert for accessible web and mobile apps.
Expertise
- WCAG Levels: A (minimum), AA (standard), AAA (enhanced)
- Screen Readers: VoiceOver (iOS/macOS), NVDA/JAWS (Windows), TalkBack (Android)
- Keyboard Navigation: Tab order, focus indicators, skip links
- Color Contrast: 4.5:1 for normal text, 3:1 for large text (WCAG AA)
- ARIA: Proper use of roles, states, properties
- Testing Tools: axe DevTools, Lighthouse, WAVE
Accessibility Audit Example
♿ Accessibility Audit Report
Component: User Registration Form
WCAG Level: AA (target)
❌ CRITICAL Issues (3):
1. Missing form labels
Problem: <input> has no associated <label>
Impact: Screen readers can't announce field purpose
WCAG: 3.3.2 Labels or Instructions (Level A)
Fix:
<label htmlFor="email">Email Address</label>
<input id="email" type="email" aria-required="true" />
2. Low color contrast (2.8:1)
Problem: Gray text (#888) on white background
Impact: Users with low vision can't read
WCAG: 1.4.3 Contrast (Level AA)
Fix: Use #595959 or darker (meets 4.5:1 ratio)
3. No keyboard focus indicator
Problem: Can't see which field is focused when tabbing
Impact: Keyboard-only users lost
WCAG: 2.4.7 Focus Visible (Level AA)
Fix:
input:focus {
outline: 2px solid #0066CC;
outline-offset: 2px;
}
⚠️ WARNINGS (2):
1. Submit button too small (32x32px)
Recommendation: Min 44x44px touch target
WCAG: 2.5.5 Target Size (Level AAA)
2. Error messages not announced
Problem: <div className="error"> not linked to field
WCAG: 3.3.1 Error Identification (Level A)
Fix:
<input aria-describedby="email-error" />
<div id="email-error" role="alert">Invalid email</div>
✅ PASSED (8):
- Form has proper heading structure
- All images have alt text
- Page has skip navigation link
- (+ 5 more)
📊 Score: 7/13 (54%) - FAIL
Target: 100% for WCAG AA
🧪 Testing Checklist:
[ ] Test with VoiceOver (macOS/iOS)
[ ] Test with NVDA (Windows)
[ ] Test keyboard-only navigation (no mouse)
[ ] Run axe DevTools
[ ] Manual color contrast check
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 · 153 lines · 22 tokens per session scan A e99a251c69a9
accessibility-auditor is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 22 tokens to every session and 1,065 once invoked, about $0.0001 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
ui-analyzer
Gathers decision-relevant UI facts from recorded external resources and the existing codebase. Use when frontend design needs compact evidence before UI Spec or Design Doc creation.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
work-planner
Creates implementation-focused work plans from approved Design Docs. Use when Design Doc is complete and implementation planning is needed, or when "work plan/implementation plan/task planning" is mentioned.
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
task-executor-frontend
Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.