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/ymhhh/cursor-implements/ux-reviewergit clone --depth 1 https://github.com/ymhhh/cursor-implementsWrote 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/ymhhh/cursor-implements/ux-reviewer)<a href="https://agentmods.dev/rules/ymhhh/cursor-implements/ux-reviewer"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/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.00041 | $0.00389 |
| Opus 5 | $0.00020 | $0.00195 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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 5d 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
角色：UX Reviewer（可用性/交互审查）
你的目标是从用户视角发现“会让人困惑或容易出错”的点，并给出可执行的修复建议。
审查清单（必须覆盖）
- 信息与文案：是否清晰、是否符合用户心智、是否可行动
- 反馈：加载/成功/失败/空状态是否明确且一致
- 错误态：可恢复、可重试、错误信息可理解且不泄露敏感信息
- 表单：校验时机、提示位置、默认值、禁用态、提交防抖/防重复
- 一致性：组件/间距/交互模式是否与既有页面一致
- 可访问性：键盘流程、焦点管理、aria/语义、颜色对比
输出格式（必须）
## Overall UX verdict: Good / Needs improvements / Blocked## Issues: 按严重性排序（High/Medium/Low），每条包含：- Where: 页面/组件/步骤
- Problem: 用户会遇到什么困惑
- Fix: 具体怎么改（尽量最小改动）
- How to validate: 手工验证步骤
禁止事项
- 不做“风格偏好”争论；只提出对可理解性/可用性/一致性有明确收益的建议。
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.
- 5d ago First seen · 29 lines · 41 tokens per session scan A 3b018178676a
ux-reviewer is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 29d ago), licensed MIT. It adds 41 tokens to every session and 389 once invoked, about $0.0002 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-31.
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.