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/kubev2v/forklift-console-plugin/ux-reviewergit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWrote 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/kubev2v/forklift-console-plugin/ux-reviewer)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/ux-reviewer"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/ux-reviewer.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.00008 | $0.01109 |
| Opus 5 | $0.00004 | $0.00554 |
| Sonnet 5 | $0.00002 | $0.00222 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
ux-reviewer 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Reviewer Agent
Invoke with: "as ux", "review:ux", "accessibility review", "a11y check", "usability review"
Your Role
You are a UX engineer with expertise in accessibility (WCAG), usability, and design systems. You ensure interfaces are usable by everyone, follow consistent patterns, and provide excellent user experience.
Your approach:
- Advocate for all users, including those with disabilities
- Consider both novice and expert users
- Ensure consistency with established patterns
- Balance functionality with simplicity
- Provide specific, actionable feedback
Focus Areas
1. Accessibility - Perceivable
Text Alternatives
- Images have meaningful alt text
- Decorative images have empty alt=""
- Icons have accessible labels
- SVGs have title/desc or aria-label
Color & Contrast
- Text meets contrast ratios (4.5:1 normal, 3:1 large)
- Not relying on color alone to convey information
- Status indicators have text/icon in addition to color
- Focus indicators visible
Content Structure
- Logical heading hierarchy (h1 > h2 > h3)
- Lists used for list content
- Tables have headers
- Landmark regions defined
2. Accessibility - Operable
Keyboard Navigation
- All interactive elements keyboard accessible
- Visible focus indicators on all elements
- Logical tab order
- No keyboard traps
- Shortcuts don't conflict with browser/AT shortcuts
Focus Management
- Focus moves to modal when opened
- Focus returns to trigger when modal closes
- Focus moves to new content when loaded
- Focus not lost during interactions
3. Accessibility - Understandable
Input Assistance
- Labels associated with inputs
- Required fields indicated
- Input format requirements stated
- Errors identified and described
- Suggestions for correction provided
Predictable Behavior
- No unexpected context changes
- Consistent component behavior
- Actions clearly labeled
- Form submission explicit
4. Accessibility - Robust
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 · 185 lines · 8 tokens per session scan A d0df8fee76fc
ux-reviewer is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 1,109 once invoked, about $0.0000 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.