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 hmcts/agentic-plugins-marketplace --skill accessibility-checkgit clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplaceWrote 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/hmcts/agentic-plugins-marketplace/accessibility-check)<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/accessibility-check"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/accessibility-check.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.00042 | $0.00557 |
| Opus 5 | $0.00021 | $0.00279 |
| Sonnet 5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
accessibility-check 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 7d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Check
Purpose
Ensure any user-facing output meets WCAG 2.1 AA. Combines automated checks (axe-core) with the manual checks that cannot be fully automated.
When to apply
- Any story that produces HTML output (pages, components, error messages, forms)
- Any story modifying navigation, focus management, or dynamic content
Automated checks (axe-core)
Add the following assertion to the integration test for every new page or component.
// Java / Selenium example
AxeBuilder axeBuilder = new AxeBuilder();
Results results = axeBuilder.analyze(driver);
assertThat(results.getViolations()).isEmpty();
// Node / Playwright example
const { checkA11y } = require('axe-playwright');
await checkA11y(page, null, { runOnly: { type: 'tag', values: ['wcag2a', 'wcag2aa'] } });
# Python / Playwright example
from axe_playwright_python.sync_playwright import Axe
results = Axe().run(page)
assert results.violations_count == 0
Manual checks (required for these scenarios)
Automation catches ~30% of issues. The rest need a human:
| Check | Guidance |
|---|---|
| Keyboard navigation | Tab through all interactive elements — logical order? |
| Focus visible | Is the focus ring visible on all interactive elements? |
| Screen reader (VoiceOver/NVDA) | Are form labels, error messages, and headings announced? |
| Colour contrast | 4.5:1 for normal text, 3:1 for large text |
| Error identification | Errors linked to fields via aria-describedby |
| Timeout warnings | User warned before session timeout with option to extend |
Failure classification
| Severity | Action |
|---|---|
| Critical | Block deployment — must fix before merge |
| Serious | Block deployment — must fix before merge |
| Moderate | Log as an issue — fix within the current sprint |
| Minor | Log as an issue — fix in the next sprint |
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.
- 7d ago First seen · 64 lines · 42 tokens per session scan A bb348931328d
accessibility-check is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 557 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.