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 skills add conorluddy/xclaude-plugin --skill accessibility-testinggit clone --depth 1 https://github.com/conorluddy/xclaude-pluginWrote 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/skills/conorluddy/xclaude-plugin/accessibility-testing)<a href="https://agentmods.dev/skills/conorluddy/xclaude-plugin/accessibility-testing"><img src="https://agentmods.dev/badge/skills/conorluddy/xclaude-plugin/accessibility-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/conorluddy/xclaude-plugin/accessibility-testing"><img src="https://agentmods.dev/badge/skills/conorluddy/xclaude-plugin/accessibility-testing.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.04812 |
| Opus 5.5 | $0.00023 | $0.01925 |
| Sonnet 5.5 | $0.00011 | $0.00962 |
| Haiku 4.5 | $0.00006 | $0.00481 |
Grade A, and why
accessibility-testing 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 1mo 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 — 813 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Testing Skill
WCAG compliance and accessibility quality assurance for iOS applications
Overview
This skill teaches accessibility-first testing strategies for iOS apps. Accessibility testing ensures apps are usable by everyone, including people with disabilities. It combines automated validation of accessibility metadata with manual verification of user experience patterns.
Why accessibility testing matters:
- Legal compliance: WCAG 2.1 is required in many jurisdictions
- User reach: 15% of population has some form of disability
- Better UX: Accessible apps are better for everyone
- SEO benefits: Better structure improves discoverability
- Cost savings: Fix issues early vs. retrofitting
When to Use This Skill
Use this skill when:
- Validating accessibility compliance before release
- Debugging VoiceOver issues or user reports
- Implementing new features that need accessibility support
- Running accessibility audits as part of CI/CD
- Testing Dynamic Type support and contrast ratios
- Verifying semantic markup and element roles
- Checking keyboard navigation and focus management
This skill covers:
- Accessibility tree analysis and interpretation
- WCAG 2.1 compliance checking (A, AA, AAA levels)
- VoiceOver testing patterns
- Dynamic Type validation
- Common accessibility violations and fixes
Quick Reference
| Task | Tool/Operation | Typical Time |
|---|---|---|
| Check accessibility quality | accessibility-quality-check |
~80ms |
| Query full accessibility tree | idb-ui-describe |
~120ms |
| Find element by label | idb-ui-find-element |
~100ms |
| Screenshot (fallback only) | screenshot |
~2000ms |
| VoiceOver simulation | Manual testing | - |
Core Principle: Accessibility Tree First
The accessibility tree IS your primary testing interface.
Unlike visual testing (screenshots), the accessibility tree reveals:
- What screen readers "see"
- Semantic structure and relationships
- Focus order and navigation paths
- Element roles and states
- Text alternatives for non-text content
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.
- 1mo ago First seen · 813 lines · 57 tokens per session scan A 66559db36e48
accessibility-testing is a skill published in the GitHub repository conorluddy/xclaude-plugin (184 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 4,812 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
argent-create-flow
Create, record, edit, replay, or repair reusable Argent flow YAML files. Use when the user asks to record or replay a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-flows. Also use before repeating three or more interactions. For one-off UI checks…
argent-ios-device-interact
Drive a physical iPhone through argent. Use when a physical iPhone is involved (a list-devices iOS entry with kind "device") and ONLY then; never for a simulator. For cable, trust, or signing problems read argent-ios-device-setup.
argent-ios-device-setup
Set up a cabled physical iPhone for argent. Use when a physical iPhone is involved (a list-devices iOS entry with kind "device") and ONLY then; never for a simulator.
goga-accept-test-assessment
Cell test coverage assessment for acceptance review.