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 lessthanseventy/excessibility --skill e11y-fixgit clone --depth 1 https://github.com/lessthanseventy/excessibilityWrote 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/lessthanseventy/excessibility/e11y-fix)<a href="https://agentmods.dev/skills/lessthanseventy/excessibility/e11y-fix"><img src="https://agentmods.dev/badge/skills/lessthanseventy/excessibility/e11y-fix/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/lessthanseventy/excessibility/e11y-fix"><img src="https://agentmods.dev/badge/skills/lessthanseventy/excessibility/e11y-fix.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.00028 | $0.02090 |
| Opus 5 | $0.00014 | $0.01045 |
| Sonnet 5 | $0.00006 | $0.00418 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade C, and why
e11y-fix scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf test/excessibility/html_snapshots/* How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Excessibility Fix - axe-core Error Reference
Quick reference for fixing axe-core/WCAG errors in Phoenix LiveView applications.
Debugging Workflow
- Run
mix excessibilityto see axe-core errors - Use
html_snapshot(view)to capture the problematic state - Read snapshot file to see exact HTML
- Apply fix from reference below
- Re-run
mix excessibilityto verify
Quick Reference
| axe-core Error | WCAG Rule | Phoenix Fix |
|---|---|---|
| Form input without label | 1.3.1 | Add <.label> or aria-label |
| Missing alt text | 1.1.1 | Add alt attribute to <img> |
| Low contrast | 1.4.3 | Adjust Tailwind colors |
| Missing lang | 3.1.1 | Add lang="en" to <html> |
| Empty link | 2.4.4 | Add link text or aria-label |
| Missing heading structure | 1.3.1 | Use proper <h1>-<h6> hierarchy |
| No skip link | 2.4.1 | Add "Skip to content" link |
Common Fixes by Category
Forms
Input without label
Error: "Form element does not have a label"
<!-- Bad -->
<input type="text" name="email" />
<!-- Good: Using Phoenix form helpers -->
<.input field={@form[:email]} type="email" label="Email address" />
<!-- Good: Manual label -->
<label for="email">Email address</label>
<input type="text" name="email" id="email" />
<!-- Good: aria-label for icon-only -->
<input type="search" aria-label="Search" />
Form without submit button
Note: LiveView forms using phx-submit often don't need a visible submit button. axe-core may flag this. You can:
- Add a submit button (even if styled invisibly)
- Configure axe-core rules to ignore this rule for specific forms
- Use
aria-labelon the form to explain the interaction
<!-- phx-submit form with hidden submit -->
<form phx-submit="save">
<.input field={@form[:name]} type="text" label="Name" />
<button type="submit" class="sr-only">Submit</button>
</form>
Required fields
<.input
field={@form[:email]}
type="email"
label="Email"
required
/>
<!-- Renders with aria-required="true" -->
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 · 340 lines · 28 tokens per session scan C dfdac9170260
e11y-fix is a skill published in the GitHub repository lessthanseventy/excessibility (42 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 2,090 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
Accessibility Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", or "vs best practices".
Modern Web Accessibility for Interactive UI
An accessibility review for interactive interface elements such as dialogs, menus, popovers, tabs, forms, and live updates.
create-db-component
Creates a new DB UX Design System component with Mitosis source, SCSS, typed model, and Playwright tests.
a11y-toolkit
Use for ALL accessibility work — WCAG 2.2 audits of URLs or HTML, real rendered contrast checks (including text over images, pixel-level), color-pair contrast and nearest passing color, European Accessibility Act / RD 1112/2018 accessibility statements, pre-deploy regression detection (accessible names, tab order)…