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 lfyxhappy/lfcode --skill accessibility-auditorgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/accessibility-auditor)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/accessibility-auditor"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/accessibility-auditor/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/lfyxhappy/lfcode/accessibility-auditor"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/accessibility-auditor.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.00350 |
| Opus 5.5 | $0.00023 | $0.00140 |
| Sonnet 5.5 | $0.00011 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
accessibility-auditor 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.
What it actually says
Accessibility Auditor
Evaluate usable access across semantics, interaction, visual presentation, and dynamic updates.
Workflow
- Identify the target route, supported platforms, user flows, viewport sizes, component states, and applicable accessibility standard or product requirement.
- Inspect the real DOM and rendered UI, not only source JSX or templates. Check landmarks, headings, labels, roles, names, descriptions, form errors, live regions, and table or dialog structure.
- Exercise keyboard-only navigation, focus visibility and order, pointer alternatives, escape and submit behavior, loading and error updates, zoom or narrow layouts, and reduced-motion behavior where applicable.
- Check color contrast, text scaling, overflow, hit targets, non-text alternatives, and status messages with available local tools. Record reproducible steps and exact elements.
- Classify findings by user impact and confidence. Suggest the smallest remediation without changing product semantics; implement only when authorized.
- Re-run the same flows after a fix and inspect browser console, page errors, and relevant automated checks.
Boundaries
- Do not claim full compliance from a limited automated scan or a single browser and viewport.
- Do not remove content, alter focus management, or weaken semantics to silence a checker.
- Redact user data from screenshots and accessibility trees when sharing evidence.
Completion check
Report finding, affected state, reproduction, expected behavior, severity rationale, verification, and coverage gaps.
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 · 28 lines · 57 tokens per session scan A e62634cb0b67
accessibility-auditor is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 350 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-09-05.
Other skills, from other repositories
design-skill
Use BEFORE building or restyling anything a user will see — web/mobile UIs, landing pages, dashboards, components, emails, AND creative work like Three.js/WebGL/canvas/SVG scenes, data-viz, games, and animations — to make it look intentional and polished, not generic; covers tokens, type, color, layout, motion…
ui-reviewer
Review rendered UI screenshots for hierarchy, spacing, readability, states, consistency, and visual slop.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
frontend-design
Give a web page or app its own look instead of a generic AI-made one: choose colors, type and layout on purpose before building, then critique the result. Use when building a new interface or reshaping an existing one.
accessibility-audit
Check a live page against the barriers that actually lock people out — keyboard, contrast, labels, focus — each with the fix.