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 commands/mn-lizard-team/aiyu-multi-agent/accessibilitygit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/commands/mn-lizard-team/aiyu-multi-agent/accessibility)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/accessibility"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/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.00000 | $0.00500 |
| Opus 5 | $0.00000 | $0.00250 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/accessibility
Digital accessibility audit and WCAG compliance. Used for ensuring products work for everyone including users with disabilities.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `accessibility-specialist`** | Skills: `clean-code, frontend-design, web-design-guidelines`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Read the agent's full instructions from
.windsurf/agents/accessibility-specialist.md(or.cursor/rules/agents/accessibility-specialist.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- Follow clean-code principles: concise, no over-engineering, self-documenting
/accessibility — Accessibility Audit & WCAG Compliance
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `accessibility-specialist`** | Skills: `clean-code, frontend-design, web-design-guidelines`
Task
Audit and fix accessibility issues. Ensure WCAG 2.2 compliance for all users.
Steps:
-
Automated Scan
- Run axe / Lighthouse accessibility audit
- Catalog violations by severity
-
Manual Testing
- Keyboard-only navigation
- Screen reader testing (NVDA / VoiceOver)
- Color contrast verification
-
WCAG Checklist
- Perceivable: alt text, captions, contrast
- Operable: keyboard, focus, timing
- Understandable: labels, errors, navigation
- Robust: valid HTML, correct ARIA
-
Remediation
- Fix critical issues first (keyboard trap, missing labels)
- Implement accessible patterns (modal focus trap, tab navigation)
- Add skip links, landmark roles
-
Verification
- Re-run automated scan
- Manual re-test
- Document compliance status
Usage Examples
/accessibility audit this page for WCAG compliance
/accessibility fix keyboard navigation issues
/accessibility add screen reader support
/accessibility check color contrast
/accessibility implement ARIA patterns for modal
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.
- 4d ago First seen · 82 lines · 0 tokens per session scan A 455bcf738c13
accessibility is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 500 tokens. 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 commands, from other repositories
brainstorm
Command dispatcher for brainstorm.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.