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 skills add blockmatic/basilic --skill audit-accessibilitygit clone --depth 1 https://github.com/blockmatic/basilicWrote 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/skills/blockmatic/basilic/audit-accessibility)<a href="https://agentmods.dev/skills/blockmatic/basilic/audit-accessibility"><img src="https://agentmods.dev/badge/skills/blockmatic/basilic/audit-accessibility.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00241 |
| Opus 5 | $0.00016 | $0.00120 |
| Sonnet 5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
audit-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.
What it actually says
Purpose and inputs
Audit the specified UI against _first/.../QUALITY.md, accessibility docs, and existing a11y tests. The Quality station owns the bar. Stay report-only unless the user asked to fix.
Steps
- Load
/f-qualityand the Quality overlay. Use the named a11y gate. If none exists, report that and run only existing repo tests. - Inspect semantic structure, keyboard access, names, and focus on changed UI.
- Run the repository's a11y or component tests. Do not declare WCAG A/AA/AAA unless the overlay names that level.
- If fixes are authorized, apply the smallest semantic/ARIA change that meets the overlay.
Verification
- Findings cite overlay, test, or rendered behavior.
- No WCAG level was invented.
- No unsolicited commit.
Handoff
List issues, the gate used, and remaining manual checks.
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 Changed · +12 lines · -3 tokens per session 4a292294dabc
- 4d ago First seen · 15 lines · 35 tokens per session scan A 35c0e0313420
audit-accessibility is a skill published in the GitHub repository blockmatic/basilic (89 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 241 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-09-03.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
ue-component-model
Create or edit the Universal Editor component configuration (component-definition.json, component-models.json, component-filters.json) for AEM Edge Delivery Services blocks. Use this skill whenever the user mentions component models, component definitions, component filters, block configuration for the Universal…