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 monkilabs/opencastle --skill accessibility-standardsgit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/accessibility-standards)<a href="https://agentmods.dev/skills/monkilabs/opencastle/accessibility-standards"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/accessibility-standards/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/skills/monkilabs/opencastle/accessibility-standards"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/accessibility-standards.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00542 |
| Opus 5.5 | $0.00021 | $0.00217 |
| Sonnet 5.5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
accessibility-standards 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 18d 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 Standards
Code must conform to WCAG 2.2 Level AA. Use people-first language ("person using a screen reader," not "blind user"); flag uncertain implementations with reasoning. Composite widget patterns (roving tabindex, aria-activedescendant) in REFERENCE.md.
Contrast
- Body text ≥4.5:1; large text (18.5px bold / 24px) ≥3:1.
- Graphics, controls, and state indicators (pressed, focus, checked) ≥3:1 against adjacent colors.
- Color is never the sole conveyor of information.
Keyboard
- No
tabindexon static elements;tabindex="-1"only for elements receiving programmatic focus. - Hidden elements must never be focusable.
- Skip link is the first focusable element, hidden via
.sr-only:not(:focus):not(:active) { clip-path: inset(50%); position: absolute; width: 1px; height: 1px; overflow: hidden; }. - Navigation:
<nav>+<ul>, NOTmenu/menubarroles. Togglearia-expanded; roving tabindex across top-level items.
Voice Access
An interactive element's accessible name must contain its visible label text — including when the name comes from aria-label.
Forms
- Required fields: asterisk in label +
aria-required="true". - Errors:
aria-invalid="true"+aria-describedbypointing at the message. - Never disable submit — show errors and focus the first invalid field.
- Disambiguate repeated labels ("Remove") with
aria-label.
Tables
<table> for static data; role="grid" with role="gridcell" nested in role="row" for interactive grids (date pickers, calendars).
Page Title
Unique per page, front-loading the unique info: "[Page] - [Section] - [Site]".
Validation
Run axe-core (axe-playwright or pa11y in CI); fix all high/critical findings and re-run until clean. Tab through the page to confirm order and visible focus. Accessibility Insights for manual passes.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 18d ago Changed · -10 tokens per session 04bee927abd9
- 1mo ago First seen · 45 lines · 63 tokens per session scan A 4dce25d742b0
accessibility-standards is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 542 once invoked, about $0.0002 per session on Opus 5.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
antislop-ui
UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion. Load with the core.
devexpress-wpf-from-screenshot
Builds a DevExpress WPF screen from a mockup — a screenshot, an image, or a Figma frame — choosing a DevExpress control per region, writing the XAML, running the app and comparing the result against the mockup. Use it even when the request never names DevExpress — "build this screen", "which control fits this layout"…
uicraft
Create, improve, audit, and polish distinctive production-grade web interfaces, including marketing/landing pages and personal portfolio sites. Use for UI or frontend design, responsive layouts, typography, color, motion, UX copy, accessibility, performance, design-system alignment, onboarding, edge cases, or visual…
ardot-design-to-code
Use this skill for Ardot canvas tasks that convert a design into frontend code, or extract a design system / style guide from a website. Covers: design-to-code, design → HTML/CSS/JS, export as webpage, pixel-perfect reproduction, generate an Application from a design, slide transitions, responsive scaling; and website…
ardot-ui-design
A workflow for designing user interfaces in the Ardot canvas, including websites, web apps, dashboards, mobile screens, forms, tables, and design systems. A user interface is the screens and controls people use to operate software.
design-skill
Use BEFORE building or restyling anything a user will see — web/mobile UIs, landing pages, dashboards, components, emails, AND creative work like Three.js/WebGL/canvas/SVG scenes, data-viz, games, and animations — to make it look intentional and polished, not generic; covers tokens, type, color, layout, motion…