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 beel-collab/presets.dev --skill ui-a11ygit clone --depth 1 https://github.com/beel-collab/presets.devWrote 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/beel-collab/presets.dev/ui-a11y)<a href="https://agentmods.dev/skills/beel-collab/presets.dev/ui-a11y"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/ui-a11y.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.00029 | $0.00583 |
| Opus 5 | $0.00015 | $0.00292 |
| Sonnet 5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ui-a11y 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 3d 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.
This is a copy
89% identical to ui-a11y — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Accessibility Audit
Overview
Part of StyleSeed, this skill audits components and pages for accessibility issues with an emphasis on the Toss seed's mobile UI patterns. It combines WCAG 2.2 AA checks with practical code fixes for touch targets, focus states, contrast, labels, and reduced motion.
When to Use
- Use when reviewing a page or component for accessibility regressions
- Use when a StyleSeed UI looks polished but has uncertain keyboard or contrast behavior
- Use when adding new interactive controls to a mobile-first screen
- Use when you want a prioritized list of issues and fixable items
Audit Areas
Perceivable
- text contrast
- non-text contrast for controls and graphics
- alt text for images
- labels for meaningful icons
- no information conveyed by color alone
Operable
- touch targets at least 44x44px
- keyboard reachability for all interactive controls
- logical tab order
- visible focus indicators
- reduced-motion support for nonessential animation
Understandable
- visible labels or
aria-labelon inputs - error text associated with the correct field
- clear wording for errors and validation
- document language set appropriately
Robust
- semantic HTML where possible
- correct use of ARIA when semantics alone are insufficient
- no faux buttons or links without the right roles and behavior
Output
Return:
- Issues found, grouped by severity
- Safe autofixes that can be applied directly
- Items that need manual review or product judgment
- A short summary of the accessibility risk level
Best Practices
- Fix semantics before layering on ARIA
- Use the design system tokens only if they still meet contrast requirements
- Treat touch target failures as real usability defects, not polish issues
- Prefer partial, verified fixes over speculative accessibility changes
Additional Resources
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.
- 3d ago First seen · 77 lines · 29 tokens per session scan A 5d852fdadceb
ui-a11y is a skill published in the GitHub repository beel-collab/presets.dev (2 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 583 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to ui-a11y, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
web-artifacts-builder-v2
Suite of tools for creating elaborate, multi-component claude.ai HTML artefacts using modern frontend web technologies (React 19, Tailwind CSS v4, shadcn/ui). Use for complex artefacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artefacts.
create-mcp-app
This skill should be used when the user asks to "create an MCP App", "add a UI to an MCP tool", "build an interactive MCP View", or needs guidance on MCP Apps SDK patterns, UI-resource registration, MCP App lifecycle, or host integration. Provides guidance for building MCP Apps with interactive UIs.
guided-demo
A pattern for adding a self-narrating (typed out) guided walkthrough to any HTML/web application. Use this skill whenever the user wants to add a guided demo, auto-narration, self-running presentation, or step-by-step tour to an HTML page, web app, prototype, HTML slide deck, dashboard, or data story.
diagrams-as-code
Use only when creating architecture diagrams with Python's diagrams library (mingrammer/diagrams).
mermaid-diagrams
Use the mermaid-diagrams skill whenever you are creating or updating mermaid diagrams. Provides guidance on mermaid best practices.