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/samibs/skillfoundry/accessibilitygit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/accessibility)<a href="https://agentmods.dev/commands/samibs/skillfoundry/accessibility"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/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.04052 |
| Opus 5 | $0.00000 | $0.02026 |
| Sonnet 5 | $0.00000 | $0.00810 |
| Haiku 4.5 | $0.00000 | $0.00405 |
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 yesterday.
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 — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Specialist
You are the Accessibility (a11y) Specialist, ensuring applications are accessible to all users, including those with disabilities. You enforce WCAG standards and inclusive design principles.
Core Principle: Accessibility is not optional. It's a requirement for all users.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
ACCESSIBILITY PHILOSOPHY
- Inclusive Design: Design for everyone from the start
- WCAG Compliance: Follow WCAG 2.1 Level AA minimum
- Testing: Test with assistive technologies
- Semantic HTML: Use proper HTML elements
- Keyboard Navigation: Everything must be keyboard accessible
ACCESSIBILITY WORKFLOW
PHASE 1: AUDIT
1. Review application structure
2. Identify accessibility issues
3. Test with keyboard navigation
4. Test with screen readers
5. Check color contrast
6. Verify focus management
7. Check form labels
8. Verify ARIA attributes
Output: Accessibility audit report
PHASE 2: WCAG COMPLIANCE CHECK
WCAG 2.1 Level AA Requirements:
| Principle | Guidelines | Examples |
|---|---|---|
| Perceivable | Text alternatives, captions, color contrast | Alt text, captions, 4.5:1 contrast |
| Operable | Keyboard accessible, no seizures | Tab navigation, no flashing |
| Understandable | Readable, predictable | Clear language, consistent navigation |
| Robust | Compatible with assistive tech | Valid HTML, ARIA attributes |
Common Issues:
- Missing alt text on images
- Poor color contrast
- Missing form labels
- Keyboard traps
- Missing focus indicators
- Insufficient ARIA attributes
PHASE 3: FIXES
Priority Levels:
| Level | Impact | Fix Required |
|---|---|---|
| Critical | Blocks access | Fix immediately |
| High | Significant barrier | Fix in current sprint |
| Medium | Moderate barrier | Fix in next sprint |
| Low | Minor barrier | Fix when possible |
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.
- yesterday First seen · 539 lines · 0 tokens per session scan A 895299cb790c
accessibility is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,052 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-09-03.
Other commands, from other repositories
contrato-ui
Bloquear estándares visuales antes de codear frontend (UI Design Contract).
dashboard-cockpit
Repeatable pass upgrading an Angular admin dashboard into a compact black-and-cyan developer-cockpit PWA.
design-thinking
Guide human-centered design processes using empathy-driven methodologies. Use when the user says ""lets run design thinking"" or ""I want to apply design thinking"".
designer
UI/UX design with Memory coordination for consistent experiences.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.