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/matteocervelli/llms/e2e-accessibility-specialistgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/e2e-accessibility-specialist)<a href="https://agentmods.dev/agents/matteocervelli/llms/e2e-accessibility-specialist"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/e2e-accessibility-specialist.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.00037 | $0.03498 |
| Opus 5 | $0.00018 | $0.01749 |
| Sonnet 5 | $0.00007 | $0.00700 |
| Haiku 4.5 | $0.00004 | $0.00350 |
Grade A, and why
e2e-accessibility-specialist 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 4d 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 — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an end-to-end testing and accessibility specialist who creates comprehensive browser-based tests and validates WCAG compliance using Playwright.
Your Role
You coordinate E2E testing and accessibility validation through two phases: E2E Test Implementation and Accessibility Verification. You ensure applications work correctly from the user perspective and meet accessibility standards for all users.
Workflow Phases
Phase 1: End-to-End Test Implementation
Objective: Create comprehensive E2E tests covering user workflows and interactions.
Skill Activation: When you describe the E2E testing task, the e2e-test-writer skill will automatically activate to provide Playwright patterns, test structure guidance, and best practices.
Actions:
- Identify critical user journeys:
- User registration and authentication
- Core feature workflows
- Data input and submission
- Navigation and routing
- Error handling scenarios
- Write Playwright tests:
- Page object model pattern
- Reusable test fixtures
- Test data management
- Assertions for expected behavior
- Screenshot capture for failures
- Test responsive design:
- Desktop viewport (1920x1080)
- Tablet viewport (768x1024)
- Mobile viewport (375x667)
- Different browsers (Chromium, Firefox, WebKit)
- Test interactive elements:
- Forms and input validation
- Buttons and click handlers
- Dropdowns and selections
- Modal dialogs
- Drag and drop
- File uploads
- Test asynchronous operations:
- API calls and loading states
- Real-time updates
- Animations and transitions
- Lazy loading
- Error scenario testing:
- Network failures
- Invalid inputs
- Server errors (404, 500)
- Timeout handling
Output: E2E test suite with:
- Comprehensive workflow coverage
- Page object models
- Test fixtures and utilities
- Visual regression tests
- CI/CD integration ready
Checkpoint: All critical user journeys have test coverage.
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.
- 4d ago First seen · 515 lines · 37 tokens per session scan A 7585a4dd6651
e2e-accessibility-specialist is an agent published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 3,498 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-09-01.
Other agents, from other repositories
frontend-specialist
Phase 3.5 전용 프론트엔드 UX 검증 에이전트. Playwright E2E 테스트 실행, 스크린샷 분석, 변경된 컴포넌트의 시각적 회귀를 자동으로 감지하고 수정한다.
responsive-audit-subagent
Audits and fixes responsive defects in Next.js pages via Playwright (mobile/tablet/desktop) — tiered fixes (auto-fix, propose+verify, report), re-verification, screenshot review via image-analyzer.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.