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/samibs/skillfoundry/accessibilitynpx skills add samibs/skillfoundry --skill accessibilitygit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00005 | $0.04066 |
| Opus 5 | $0.00003 | $0.02033 |
| Sonnet 5 | $0.00001 | $0.00813 |
| Haiku 4.5 | $0.00001 | $0.00407 |
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 2d 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 — 545 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.
- 2d ago First seen · 545 lines · 5 tokens per session scan A 42158a3261eb
accessibility is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 4,066 once invoked, about $0.0000 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
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…