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.
git clone --depth 1 https://github.com/xcodethink/open-claude-code-skillsWrote 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/commands/xcodethink/open-claude-code-skills/ui-test)<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/ui-test"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/ui-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/ui-test"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/ui-test.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.00516 |
| Opus 5.5 | $0.00013 | $0.00206 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
ui-test 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 1mo 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
ui-test — UI 还原 + 浏览器实测
用户输入 /ui-test $ARGUMENTS 触发 代码改 + 浏览器实测(防"改完没真去看"陷阱)。
⭐ "真去浏览器看 / 评判 UI"默认用 (自研 AI 浏览器审计器, 已注册为 MCP server + 全局 link; 见全局 CLAUDE.md 顶部铁律)。
- 优先: MCP 工具 (see/judge/compare) >
<ui-audit-tool> explore --url <url> --goal <..> --criteria <..>/<ui-audit-tool> run> 自写 Playwright<ui-audit-tool> doctor自检; key 在 <该工具仓>/.env; 首次AUDIT_AUTO_CONSENT=1- 下面的 Playwright/手动流程仅作 确实不可用时的兜底, 不要默认走它。
立刻读取并完整加载:
~/.claude/prompts/lib/06-设计/UI还原浏览器实测.md
按其"行为契约"段严格执行:
- 按设计稿改代码
- 启动 dev server,真去浏览器看(不只是"类型检查通过 = 完成")
- 跑通golden path + 边缘 case(空状态 / 错误 / 加载 / 离线)
- 多设备 / 多浏览器(至少 Chrome + Safari + 手机宽度)
- 监控"是否破坏了其他功能"
无法跑浏览器(headless 环境)→ 明确说不能,不假装完成。
参数含修饰符 → 叠加对应文件。
核心契约:类型检查 / 测试套件验代码正确性,不验功能正确性。UI 改动不去浏览器看 = 没做完。
参数: $ARGUMENTS
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.
- 1mo ago First seen · 32 lines · 0 tokens per session scan A 5c91779c7cae
ui-test is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 516 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
design-review
Review code, screenshots, or visual artifacts against visual design principles — identifies violations and suggests research-backed improvements.
saas-review
Review the current code or component against SaaS design principles — identifies violations and suggests improvements.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.
extract-foundations-from-screens
Extract canonical foundations docs (color, typography, spacing, radii) from a batch of existing SCREENSPECs. Re-runs only add new tokens and route conflicts to a Review queue. Use when SCREENSPECs already document raw values and need converging into role tokens. Do not use when foundations are already curated and…
screen-spec
Generate a screen specification from a Figma frame using MCP tools (getdesigncontext, getscreenshot), matching the SCREENSPEC.md template (layout, states). Use when documenting a specific screen. Do not use when the screen has no Figma frame or the spec already exists, for 6 or more screens (use screen-spec-fleet), or…
a11y
You are a WCAG 2.1 Level AA accessibility specialist. You audit user interfaces for perceivable, operable, understandable, and robust compliance. You have zero tolerance for "we'll add a11y later" — accessibility is a launch requirement, not a polish step.