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 andr-ca/agentharness --skill accessibilitygit clone --depth 1 https://github.com/andr-ca/agentharnessWrote 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/andr-ca/agentharness/accessibility)<a href="https://agentmods.dev/skills/andr-ca/agentharness/accessibility"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/accessibility/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/andr-ca/agentharness/accessibility"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/accessibility.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.00044 | $0.01238 |
| Opus 5.5 | $0.00018 | $0.00495 |
| Sonnet 5.5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
accessibility 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
This skill is self-contained for day-to-day use. Deeper reference (needs
the full harness checkout): patterns/accessibility/README.md (full
examples including ARIA live regions and APG patterns). External
canonical sources: WCAG 2.2 and the
WAI-ARIA Authoring Practices.
Target: WCAG 2.2 Level AA.
The first rule: don't use ARIA if a native element exists
A native <button>, <a href>, <input>, <label>, <nav>, or
<table> brings keyboard behavior, focus management, and the correct
role/state for free. role="button" + tabindex + keyboard handler is
a liability you now own forever.
<!-- Good: browser handles focus, Enter, Space, and role automatically -->
<button type="button" onclick="save()">Save</button>
<!-- Avoid: you must re-implement everything the native button provides -->
<div role="button" tabindex="0" onclick="save()" onkeydown="handleKey(event)">Save</div>
Perceivable
- Text alternatives. Meaningful images:
altdescribing purpose. Decorative images:alt="". Icon-only controls:aria-labelor visually-hidden text. - Contrast. Body text ≥ 4.5:1 against background. Large text (≥ 24px, or ≥ 18.66px bold) and UI components/graphics ≥ 3:1. Verify computed colors — don't eyeball.
- Color alone is not enough. A red border and an error text/icon — not red alone.
Operable
- Keyboard. All interactive elements must be reachable by Tab, in
logical order, with no keyboard trap.
tabindex="0"for natural order;tabindex="-1"for programmatic-only focus; never positive values. - Visible focus. Never
outline: nonewithout a clearly visible replacement. Keyboard users navigate by it. - Skip link. First focusable element on pages with repeated
navigation:
<a href="#main">Skip to main content</a>. - Target size. Interactive targets ≥ 24×24 px (WCAG 2.2 §2.5.8), with adequate spacing if smaller.
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 · 119 lines · 44 tokens per session scan A 7ca0d8abc785
accessibility is a skill published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 1,238 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-31.
Other skills, from other repositories
static-web-artifacts-builder
Build self-contained static HTML artifacts opened in a browser: interactive diagrams, dashboards, infographics. Pure HTML5+CSS3+inline SVG, zero toolchain. Triggers on: "interactive HTML", "open in browser", "HTML artifact", "visual dashboard", "HTML infographic". NOT for PNG/SVG output, use concept-to-image. NOT for…
web-design-system-foundation
Use when the repository has no design system yet (no tokens, no component library - a new site/app, an "Apply design system" task, or a task that asks for one), before building any page section - writes the approved design system's generated files from getdesignsystem (files true) and builds the tokens on them when…
screen-mockup-html
Use when you draw a screen as HTML mockup documents (one per variant) - the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task.
responsive-layout
Use when you build or change a layout, page, section, navigation, table, form or image - mobile-first rules, breakpoints and the overflow traps.
accessibility-basics
Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs/menus, visible focus, and never color as the only signal.
frontend-ui-audit
Frontend UI consistency audit for React + Tailwind codebases. Use when reviewing component refactors, UI cleanup batches, or answering "should this use the design system?" — checks design-system adoption, arbitrary Tailwind values vs tokens, hardcoded sizes and colors, accessibility basics, and repeated visual…