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 rules/thematters/matters-web/accessibilitygit clone --depth 1 https://github.com/thematters/matters-webWhat 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.00556 | $0.00556 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility (A11Y)
Matters Web follows these accessibility best practices to ensure the platform is usable by everyone.
Semantic HTML
Use semantic HTML elements to provide meaning and structure:
<header>: Page header or section header<nav>: Navigation menus<main>: Main content area<section>: Standalone section of content<article>: Self-contained composition (e.g., blog post)<aside>: Content tangentially related to the content around it<footer>: Footer for page or section<figure>and<figcaption>: Images with captions<button>: For interactive elements that perform an action<a>: Only for navigation to a new page or location within page
Non-semantic elements like <div> and <span> should only be used when no semantic element is appropriate.
WAI-ARIA
Use ARIA attributes when HTML semantics aren't sufficient:
role: Define the purpose of an element (e.g.,role="alert",role="dialog")aria-label: Provide an accessible name (e.g.,aria-label="Close dialog")aria-labelledby: Reference another element as the labelaria-describedby: Reference descriptive text for an elementaria-expanded: Indicate if expandable element is open or closedaria-hidden: Hide decorative elements from screen readersaria-live: For dynamically updating content
Focus Management
- Ensure all interactive elements are keyboard accessible
- Maintain a logical tab order
- Make focus visible with clear focus indicators
- Trap focus inside modals with
<FocusLock>component byreact-focus-lock
Images
- Always include
alttext for images - Use empty
alt=""for decorative images
Forms
- Associate labels with form controls using
htmlFor - Group related form elements with
<fieldset>and<legend> - Provide clear error messages and validation
- Use appropriate input types (e.g.,
type="email")
Components
Our accessible components include:
<Button>: Accessible button component<Dialog>: Accessible modal dialog with focus management<Form>: Accessible form controls with proper labeling
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 · 71 lines · 556 tokens per session scan A f28d22e3395a
accessibility is a cursor rule published in the GitHub repository thematters/matters-web (86 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 556 tokens to every session, about $0.0028 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 cursor rules, from other repositories
tutorial-system-guide
This guide documents the complete tutorial infrastructure in Windmill's frontend, enabling developers to create new interactive tutorials without re-exploring the codebase.
windmill-overview
Windmill is an open-source developer platform for building internal tools, API integrations, background jobs, workflows, and user interfaces. It offers a unified system where scripts are automatically turned into sharable UIs and can be composed into flows or embedded in custom applications.
api-arena-project-progress
Estado actual del proyecto API Arena - servicios implementados, lo que falta, y arquitectura.
api-arena-project-spec
Plataforma educativa competitiva donde estudiantes compiten creando APIs. Evaluación automática mediante tests funcionales, rendimiento, diseño REST y review IA. Incluye Replay system y Multiplayer mode.
api-arena-no-volume-recreation
CRÍTICO — entorno de PRODUCCIÓN. Nunca recrear/borrar volúmenes Docker. Los cambios de BD se aplican SIEMPRE con migraciones idempotentes en caliente.
api-arena-commit-workflow
Commits pequeños y frecuentes, uno por feature/fix cuando funcione y esté verificado.