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 skills add Xiaowen-Jiang/agent-enterprise --skill ui_ux_reviewgit clone --depth 1 https://github.com/Xiaowen-Jiang/agent-enterpriseWrote 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/skills/xiaowen-jiang/agent-enterprise/ui_ux_review)<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/ui_ux_review"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/ui_ux_review/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/skills/xiaowen-jiang/agent-enterprise/ui_ux_review"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/ui_ux_review.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.00016 | $0.00465 |
| Opus 5 | $0.00008 | $0.00233 |
| Sonnet 5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
UI/UX Review 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 10d 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
Process
- Read the UI code — HTML/CSS/JS, component structure, layout
- Heuristic evaluation (Nielsen's 10):
- Visibility of system status
- Match between system and real world
- User control and freedom (undo, cancel)
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize and recover from errors
- Help and documentation
- Accessibility check (WCAG 2.1):
- Color contrast (4.5:1 for text, 3:1 for large text)
- Keyboard navigation (all interactive elements reachable)
- Screen reader compatibility (ARIA labels, semantic HTML)
- Focus indicators visible
- Responsive design — Mobile, tablet, desktop breakpoints
- Interaction patterns — Loading states, empty states, error states
Output Format
## UI/UX Review: [Component/Page Name]
### Usability Issues
| Issue | Severity | Heuristic | Recommendation |
|-------|----------|-----------|----------------|
| No loading indicator on submit | Medium | Visibility of status | Add spinner/progress bar |
### Accessibility Issues
| Issue | WCAG Level | Recommendation |
|-------|------------|----------------|
| Missing alt text on images | A | Add descriptive alt attributes |
### Positive Patterns
- [What's working well]
### Recommendations (Priority Order)
1. [Most impactful improvement]
Guidelines
- Test with keyboard-only navigation — can you reach everything without a mouse?
- Check color contrast with a contrast checker tool
- Verify all form inputs have labels (not just placeholders)
- Ensure error messages are near the error source, not just at the top
- Check empty states — what does the user see when there's no data?
- Verify that destructive actions have confirmation dialogs
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.
- 10d ago First seen · 62 lines · 16 tokens per session scan A 70e48054adf2
UI/UX Review is a skill published in the GitHub repository Xiaowen-Jiang/agent-enterprise (52 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 465 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-08-30.
Other skills, from other repositories
ce-prototype
Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already works, not…
ce-polish
Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.
sage-review
Deep, platform-neutral code review for PRs and CRs in ONE thorough single pass — design reasoning (Problem Worth Solving & Solution Fit) as one dimension alongside the 9 code-level dimensions, with chain-of-consequences, self-critique, and draft-only comments. The single app-owned source of truth.
deck-blueprint
A presentation design template for explaining architecture and process pipelines on a cream-colored, blueprint-style background.
demand-elegance
Challenges hacky fixes on non-trivial changes.
design-loop
Use when something must be built well and there is a real reference it should beat: turn what makes the reference good into measured mechanisms, then run a builder and three fresh-context critics until all three pass. Fires on 'design loop', 'make it as good as ', 'it looks generic'. NOT keeping an already-won look…