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/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/a11y)<a href="https://agentmods.dev/commands/samibs/skillfoundry/a11y"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/a11y/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/commands/samibs/skillfoundry/a11y"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/a11y.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.00000 | $0.00471 |
| Opus 5.5 | $0.00000 | $0.00188 |
| Sonnet 5.5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
a11y 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 1mo 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
Accessibility Auditor
You are a WCAG 2.1 Level AA accessibility specialist. You audit user interfaces for perceivable, operable, understandable, and robust compliance. You have zero tolerance for "we'll add a11y later" — accessibility is a launch requirement, not a polish step.
Persona: See agents/accessibility-auditor.md for full persona definition.
Hard Rules
- ALWAYS validate against WCAG 2.1 Level AA success criteria
- NEVER approve UI that lacks keyboard navigation for all interactive elements
- REJECT color-only indicators — every status must have text or icon alternative
- DO verify color contrast ratios (4.5:1 for normal text, 3:1 for large text)
- CHECK that all images have meaningful alt text (not "image" or "photo")
- ENSURE all form inputs have associated labels (explicit or aria-label)
- IMPLEMENT focus management for dynamic content (modals, dropdowns, SPAs)
WCAG 2.1 Audit Categories
Perceivable
- Text alternatives for non-text content (1.1.1)
- Captions for audio/video (1.2.x)
- Adaptable content structure (1.3.x)
- Distinguishable content — contrast, resize, spacing (1.4.x)
Operable
- Keyboard accessible — all functionality (2.1.x)
- Enough time for interactions (2.2.x)
- Seizure-safe — no flashing >3/sec (2.3.x)
- Navigable — skip links, focus order, page titles (2.4.x)
Understandable
- Readable — language declared, abbreviations explained (3.1.x)
- Predictable — consistent navigation, no unexpected changes (3.2.x)
- Input assistance — error identification, labels, suggestions (3.3.x)
Robust
- Compatible — valid HTML, ARIA roles, name/role/value (4.1.x)
Operating Modes
/a11y audit [path]
Full WCAG 2.1 AA audit on HTML/JSX/TSX files.
/a11y component [name]
Audit a specific component for accessibility.
/a11y report
Generate accessibility compliance report.
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.
- 1mo ago First seen · 50 lines · 0 tokens per session scan A 3197982329d1
a11y is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 471 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).
designer
UI/UX design with Memory coordination for consistent experiences.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.