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 agentmods add skills/volomydyr/design-engineer-plugin/ui-accessibilitynpx skills add volomydyr/design-engineer-plugin --skill ui-accessibilitygit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWrote 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/volomydyr/design-engineer-plugin/ui-accessibility)<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/ui-accessibility"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/ui-accessibility.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 | $0.00038 | $0.01351 |
| Opus 5 | $0.00019 | $0.00675 |
| Sonnet 5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
ui-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 5d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Review
Why This Matters
Accessibility is a UX improvement, not just a compliance requirement. Principles like Fitts's Law (larger targets are easier to hit) and Cognitive Load theory (simpler interfaces reduce mental effort) apply to every user – not just those with disabilities. Building accessible products creates better experiences for everyone.
Interaction Method
If AskUserQuestion is available, use it for all prompts below.
If not, present each question as a numbered list and wait for a reply before proceeding. For multiSelect questions, accept comma-separated numbers (e.g. 1, 3). Never skip or auto-answer without explicit user consent.
Step 1: Determine Review Scope
question: "What are you reviewing for accessibility?"
header: "Review Scope"
options:
- label: "Figma designs (pre-implementation)"
description: "Check designs before code is written"
- label: "Implemented screens (code audit)"
description: "Audit existing code for accessibility issues"
- label: "Live application (URL or device)"
description: "Test a running application"
- label: "Specific component"
description: "Focus on one component or interaction"
- label: "HTML prototype"
description: "Check an HTML prototype file for accessibility issues"
When "HTML prototype" is selected, read the HTML file at the path the user provides (default: .design-engineer-plugin/prototype/prototype.html). Run the full accessibility checklist with particular attention to contrast ratios, touch/click target sizes, keyboard navigation, screen reader support (semantic HTML, ARIA labels), and heading hierarchy.
Step 2: Run the Accessibility Audit
Use the comprehensive checklist from accessibility-checklist.md covering:
Touch and Click Targets
- Minimum tap target size: 56 points (based on Fitts's Law – smaller targets require more precision and slow users down)
- Adequate spacing between interactive elements to prevent accidental taps
- Touch targets that extend beyond visible boundaries where needed for small icons
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 141 lines · 38 tokens per session scan A d103070f3ec3
ui-accessibility is a skill published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 1,351 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…