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/ocean-industries-concept-lab/openbridge-webcomponents/a11ygit clone --depth 1 https://github.com/Ocean-Industries-Concept-Lab/openbridge-webcomponentsWrote 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/rules/ocean-industries-concept-lab/openbridge-webcomponents/a11y)<a href="https://agentmods.dev/rules/ocean-industries-concept-lab/openbridge-webcomponents/a11y"><img src="https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/a11y.svg" alt="Measured on agentmods" 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.03541 |
| Opus 5 | $0.00000 | $0.01770 |
| Sonnet 5 | $0.00000 | $0.00708 |
| Haiku 4.5 | $0.00000 | $0.00354 |
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 6d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Instructions
These instructions apply to all interactive UI components and automation components. Target: WCAG 2.1 AA, plus WCAG 2.2 § 2.5.8 for pointer target size (§ 7) — 2.1 has no target-size criterion at AA level. The primary focus is keyboard navigation — every new interactive component must be fully operable without a mouse.
Display-only SVG instruments (navigation-instruments, building-blocks, bars-graphs) are out of scope unless they expose interactive affordances (e.g. draggable setpoints).
1. Follow the WAI-ARIA Authoring Practices
Keyboard behaviour rarely needs to be designed from scratch. Before writing a key handler, look the widget up in the WAI-ARIA Authoring Practices Guide (APG) patterns — it is the industry-standard reference for how each widget type is expected to behave, and it is what keyboard and screen-reader users have already learned from every other application. A component that invents its own bindings is usually harder to use, not more discoverable.
This section is guidance, not a conformance checklist: it describes the default worth starting from, and it assumes you will exercise judgement. Work down the ladder and stop at the first step that applies:
- An APG pattern matches the widget. Follow it — its roles, its states, and its keyboard interaction table — as closely as the component allows. Leaving out part of a pattern is a normal call to make (some behaviours the APG lists are optional, others are not worth the complexity for a given component); just note what you left out in the implementation's JSDoc, so an intentional gap doesn't read as a bug.
- No exact match, but a close one exists. Adapt the closest pattern rather than starting over, and keep its key bindings for the parts that do map. Say which pattern you adapted and where the component departs from it.
- Nothing in the APG applies. Design a pattern, then write it down in the component's JSDoc and the PR body. A home-grown pattern should still reuse conventional keys with their conventional meanings (
Enter/Spaceactivate,Escapecancels or backs out, arrow keys move within a composite widget), avoid overriding keys the browser or assistive technology owns, expose its state through ARIA so it is announced rather than only visible, and never leave the user stuck in a keyboard trap.
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.
- 6d ago First seen · 147 lines · 0 tokens per session scan A 544615093954
a11y is a cursor rule published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (92 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,541 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-08-30.
Other cursor rules, from other repositories
cursorrules
Read and follow AGENTS.md for all development conventions.
static-analysis
Run local static analysis and fix new issues before finishing a task.
sigil-conventions
All CSS variables use the --s- prefix: var(--s-primary), var(--s-surface), etc.
backend
Backend API coding standards with clean architecture (Router/Service/Repository pattern).
market
Market research standards - trap detection, keyless-first sourcing, LAW enforcement, deterministic compute.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.