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 emaraschio/cursor-commands --skill accessibility-auditgit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/emaraschio/cursor-commands/accessibility-audit)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/accessibility-audit"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/accessibility-audit.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.00014 | $0.00388 |
| Opus 5 | $0.00007 | $0.00194 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
accessibility-audit 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 7d 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
Overview
Perform comprehensive accessibility (a11y) audit of the current UI code to ensure compliance with WCAG guidelines and provide an inclusive user experience.
Steps
- WCAG Compliance
- Check conformance to WCAG 2.1 guidelines (A, AA, AAA levels)
- Verify proper semantic HTML structure
- Ensure keyboard navigation support
- Review color contrast and visual accessibility
- Screen Reader Support
- Validate ARIA labels and descriptions
- Check heading hierarchy and structure
- Ensure form labels and error messages are accessible
- Review dynamic content announcements
- Interactive Elements
- Verify focus management and visible focus indicators
- Check tab order and keyboard shortcuts
- Ensure interactive elements are properly sized
- Review modal and dialog accessibility
- Testing & Tools
- Suggest automated accessibility testing tools
- Provide manual testing procedures
- Create accessibility test cases
- Recommend browser extensions and validators
- Remediation
- Provide specific code fixes for each issue
- Include ARIA attributes and semantic improvements
- Suggest alternative approaches for complex interactions
- Create accessible component patterns
Accessibility Audit Checklist
- WCAG compliance verified
- Screen reader support validated
- Interactive elements accessible
- Testing tools recommended
- Remediation code provided with examples
Guardrails
- Change only accessibility issues; do not touch unrelated code.
- Verify keyboard navigation and screen reader behavior, not only automated scans.
- Do not print or commit secrets, tokens, or credentials found while auditing UI code; flag their location instead.
- Do not commit, push, or merge changes without explicit consent.
What ships with it
3 files 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.
- 7d ago First seen · 51 lines · 14 tokens per session scan A f94a66f12972
accessibility-audit is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 388 once invoked, about $0.0001 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-31.
Other skills, from other repositories
design-review
Stress-test a plan or design against domain language, docs, and code. Ask hard questions one at a time. Update CONTEXT.md and ADRs as decisions crystallize. Use when you already have a draft plan or spec and want to find gaps before implementation.
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
ijfw-design
Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.
grok-build-supervisor
Initialize the persistent local proxy, then immediately ensure a visible Grok Build TUI for the current workspace when /grokexecute on activates, and continuously supervise that coding-agent session through a user-level Supervisor daemon as the user sends work, waits for completion, reconnects from another host task…
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
grok-executor-mode
Task-local execution policy applied to ordinary user tasks only after an exact /grokexecute on; the host agent then plans, supervises, corrects, and verifies while all implementation and workspace-mutating execution goes through Grok Build Supervisor. Never activate or deactivate from ordinary requests, task text…