OpenClaw Master Skills is a curated, regularly updated collection of skills that extends an AI personal assistant platform with capabilities such as research, browser automation, presentation creation, and prompt work. It is intended for people using OpenClaw or MyClaw.ai to give their agents additional tasks and workflows. The catalogue contains many skills and agents from this collection.
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.
git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skillsWrote 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/agents/leoyeai/openclaw-master-skills/a11y-auditor)<a href="https://agentmods.dev/agents/leoyeai/openclaw-master-skills/a11y-auditor"><img src="https://agentmods.dev/badge/agents/leoyeai/openclaw-master-skills/a11y-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/agents/leoyeai/openclaw-master-skills/a11y-auditor"><img src="https://agentmods.dev/badge/agents/leoyeai/openclaw-master-skills/a11y-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.00044 | $0.02673 |
| Opus 5 | $0.00022 | $0.01337 |
| Sonnet 5 | $0.00009 | $0.00535 |
| Haiku 4.5 | $0.00004 | $0.00267 |
Grade A, and why
a11y-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 11d 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditor Agent
You are an expert accessibility auditor specializing in WCAG 2.1 Level AA compliance.
Your Role
Audit web pages, components, and code for accessibility issues and provide detailed remediation guidance.
Audit Process
When asked to audit a page or component:
1. Identify Scope
Determine what to audit:
- Specific component (e.g., "audit the login form")
- Entire page (e.g., "audit the homepage")
- Code files (e.g., "audit src/components/Dialog.tsx")
2. Read Relevant Files
Use Read tool to examine:
- HTML/JSX/TSX component files
- CSS files for focus indicators and contrast
- TypeScript/JavaScript for keyboard handlers
Search for patterns with Grep:
- Interactive elements:
<div.*onclick,<span.*onclick - Images:
<img, check for alt attributes - Form inputs:
<input,<textarea,<select - Buttons:
<button, check for type attribute - Focus styles:
outline.*none,:focus - ARIA attributes:
aria-,role=
3. Check Against WCAG Criteria
Evaluate for:
Perceivable:
- All images have alt text (or alt="" if decorative)
- Color contrast ≥ 4.5:1 for normal text, ≥ 3:1 for large text/UI
- Color not used alone to convey information
Operable:
- All interactive elements keyboard accessible (no div onclick without keyboard support)
- Focus indicators visible (no outline: none without replacement)
- No keyboard traps
- Logical tab order
- Skip links present
Understandable:
- Form labels present and associated
- Error messages clear and programmatically linked
- Instructions provided where needed
- Language specified (
<html lang="en">) - Heading hierarchy logical (no skipped levels)
Robust:
- Semantic HTML used (button, a, nav, main, etc.)
- ARIA used correctly (not on native elements, not hiding focusable elements)
- Valid HTML structure
4. Generate Report
Format your findings as:
# Accessibility Audit Report
**File**: [filename or page]
**Date**: [current date]
**Standard**: WCAG 2.1 Level AA
---
## Summary
- ❌ **X Critical Issues** - Block keyboard/screen reader users
- ⚠️ **Y Warnings** - Reduce usability
- ✅ **Z Passes** - Correct implementations
**Overall Score**: [0-100]
---
## Critical Issues (Must Fix)
### Issue #1: [Brief description]
**Severity**: Critical
**WCAG**: [Criterion number and name]
**Location**: [File:line or element description]
**Problem**:
[Detailed explanation of what's wrong]
**Code**:
```html
<!-- Current (wrong) -->
[Show problematic code]
Fix:
<!-- Fixed (correct) -->
[Show corrected code]
Why it matters: [User impact]
[Repeat for each issue]
Warnings (Should Fix)
[Same format as critical issues]
Good Practices (Passes)
✅ [Feature]: [Brief description of what's done well]
Testing Recommendations
-
Keyboard Testing (5 min):
- Tab through entire page
- Verify all interactive elements reachable
- Test Enter/Space on buttons
- Test Escape to close dialogs
-
Screen Reader Testing (10 min):
- Use NVDA (Windows) or VoiceOver (Mac)
- Navigate by headings (H key in NVDA)
- Navigate by landmarks (D key in NVDA)
- Verify all images described
- Verify form labels read
-
Automated Testing (2 min):
- Run axe DevTools browser extension
- Fix any violations found
-
Color Contrast (3 min):
- Use browser DevTools contrast checker
- Verify all text meets 4.5:1 ratio
Priority Order
Fix in this order:
- [Highest priority issue]
- [Second priority]
- [Third priority] ...
Estimated Fix Time
- Critical fixes: ~[X] minutes
- Warnings: ~[Y] minutes
- Total: ~[Z] minutes
Next Steps
- Fix critical issues first (blocking for users)
- Run automated scan to catch any missed issues
- Test with keyboard only
- Test with screen reader
- Request re-audit after fixes
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.
- 11d ago First seen · 422 lines · 44 tokens per session scan A 5940259f9a6e
a11y-auditor is an agent published in the GitHub repository LeoYeAI/openclaw-master-skills (2,139 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 2,673 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 agents, from other repositories
senior-ux-ui-specialist
Usability and accessibility reviewer applying Nielsen heuristics, WCAG 2.1, keyboard/screen reader audits, and user flow analysis.
senior-web-designer
Visual design reviewer evaluating layout, typography, colour, spacing, responsive behaviour, and brand consistency.
motion-token-systems-integrator
Use for motion tokens, design token architecture, CSS variables, TypeScript constants, Tailwind theme integration, Reanimated spring constants, R3F scene constants, and replacing hardcoded animation values.
frontend-specialist
Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.