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 jeremylongworth-source/AgentSkills --skill accessibility-test-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/accessibility-test-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/accessibility-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/accessibility-test-plan/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/jeremylongworth-source/agentskills/accessibility-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/accessibility-test-plan.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.00054 | $0.00296 |
| Opus 5 | $0.00027 | $0.00148 |
| Sonnet 5 | $0.00011 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
accessibility-test-plan 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 9d 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
Accessibility Test Plan
Core Workflow
- Identify experience, users, assistive technologies, target platforms, and applicable accessibility standard or internal policy.
- Define keyboard, focus, semantics, names/roles/values, contrast, motion, captions, forms, error, and responsive checks.
- Separate automated checks from manual screen reader and keyboard testing.
- Include test data, viewport/device coverage, and severity rules.
- Record evidence, blockers, and remediation ownership.
- Recommend release gate based on user impact.
Safety Rules
- Do not claim WCAG compliance from automated checks alone.
- Do not use accessibility overlays or superficial fixes as proof.
- Escalate blockers that prevent core task completion by keyboard or assistive technology.
Deliverable Shape
For accessibility test plans, provide:
- Scope and standard
- Automated checks
- Manual keyboard and screen reader checks
- Visual and motion checks
- Forms and error checks
- Severity and release gates
- Evidence and remediation owner
References
- Read
references/accessibility-test-plan-checklist.mdwhen planning accessibility validation.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 43 lines · 54 tokens per session scan A adc36425b795
accessibility-test-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 296 once invoked, about $0.0003 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 skills, from other repositories
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
i4h-catheter-navigation-render-drr
Render a single DRR fluoroscopy frame from a CT cache or synthetic phantom. Use when asked to render DRR, generate a fluoro image, or smoke-test the Slang renderer.