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/oriolshhh/runware-image-mcp/accessible-ui-engineeringgit clone --depth 1 https://github.com/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/accessible-ui-engineering)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/accessible-ui-engineering"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/accessible-ui-engineering.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.00017 | $0.00460 |
| Opus 5 | $0.00009 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
accessible-ui-engineering 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: accessible-ui-engineering
Accessible UI Engineering
Purpose
Make accessibility part of implementation and verification rather than a late lint pass.
When to use it
- During implementation and review of every interactive or content-bearing UI.
Instructions
- Use native elements and semantics first; add ARIA only to express behavior native HTML cannot represent.
- Give every control an accessible name, state, role, target size, and logical keyboard operation. Never remove focus visibility.
- Manage focus on dialogs, navigation, errors, deletion, and dynamically added content; restore it to a sensible location.
- Verify contrast, non-color cues, text resize/zoom, reflow, reduced motion, captions/alternatives, and high-contrast behavior when relevant.
- Associate form labels, instructions, errors, and summaries; preserve entered values and move focus to actionable recovery.
- Run available automated accessibility checks, then manually test keyboard, focus order, accessible names, announcements, and representative screen-reader paths.
- Cite applicable WCAG criteria for blockers and distinguish automated coverage from manual or untested coverage.
Output format
Implementation notes and an accessibility report: tested paths, automated and manual evidence, blockers, WCAG references, fixes, and untested assistive technology.
Anti-patterns
- Treating zero automated findings as accessible.
- Adding ARIA to compensate for a non-semantic control.
- Subjective aesthetic feedback labelled as an accessibility blocker.
Verification checklist
- The complete task is keyboard-operable with visible focus and sensible recovery.
- Names, roles, states, contrast, zoom/reflow, motion preference, and errors were exercised.
Apply
context-discoverybefore broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read.agent/context/routing.md, load only relevant summaries, and verify critical claims against source.
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 · 50 lines · 17 tokens per session scan A bcfc4190746f
accessible-ui-engineering is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 460 once invoked, about $0.0001 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 cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.