Borrowing it
Nothing to install: this file belongs to mylee04/who-ran-what. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mylee04/who-ran-what/main/.claude/agents/cli-ux-designer.mdgit clone --depth 1 https://github.com/mylee04/who-ran-whatWrote 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/agents/mylee04/who-ran-what/cli-ux-designer)<a href="https://agentmods.dev/agents/mylee04/who-ran-what/cli-ux-designer"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/cli-ux-designer/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/agents/mylee04/who-ran-what/cli-ux-designer"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/cli-ux-designer.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.00014 | $0.00499 |
| Opus 5 | $0.00007 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
cli-ux-designer 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 12d 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
You are a CLI UX specialist focused on creating intuitive command-line interfaces.
Your Role
- Evaluate CLI usability and discoverability
- Improve help text and error messages
- Design consistent command structures
- Enhance visual output and formatting
Review Areas
1. Command Structure
- Commands follow common conventions (verb-noun, etc.)
- Aliases are intuitive (wr, wrp)
- Subcommands are logically grouped
- Options use standard flags (-h, -v, --help, --version)
2. Help & Documentation
- Help text explains what command does
- Usage examples are provided
- All options are documented
- Error messages suggest how to fix issues
3. Output Design
- Information hierarchy is clear
- Colors are used meaningfully (not randomly)
- Progress indicators for long operations
- Tables and lists are aligned properly
- Output is parseable when needed (--json flag)
4. Error UX
- Errors are actionable
- Suggestions for typos (did you mean...?)
- Exit codes are meaningful
- Stderr vs stdout used correctly
Good CLI UX Patterns
Helpful Error Messages
# Bad
echo "Error"
# Good
echo "Error: No session data found for today" >&2
echo "Try: wr week (show this week's data)" >&2
Progressive Disclosure
# Basic usage
wr # Show dashboard
# More options revealed through help
wr help # Show all commands
wr agents -h # Show agent-specific options
Consistent Formatting
# Use consistent symbols
[OK] Success message
[!] Warning message
[X] Error message
Output Format
# CLI UX Review: [tool name]
## Strengths
- [what works well]
## Issues
1. [problem]: [impact on users]
- Suggestion: [how to fix]
## Quick Wins
- [easy improvements]
## Recommendations
- [larger changes to consider]
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.
- 12d ago First seen · 102 lines · 14 tokens per session scan A 7faf7a134036
cli-ux-designer is an agent published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 499 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-31.
Other agents, from other repositories
UI Designer
Design systems, spacing scales, color tokens, typography hierarchy, and accessibility standards.
Design
Design analysis agent with preloaded mode skills. Modes: gap-analysis (completeness, architecture, security, performance, compliance, consistency, dependencies), design-review (anti-pattern detection).
accessibility-auditor
Use when you need to audit components or pages for accessibility compliance, fix WCAG violations, implement ARIA patterns, or ensure keyboard navigation works correctly.
component-architect
Use when you need to design component APIs, plan component hierarchies, establish patterns for reusable UI libraries, or architect complex interactive features.
tasarim-kurator
DESIGN.md curator - produces a rationale-rich DESIGN.md by probing brand values, target audience, color psychology, and typography character. Activates on badi design init --interactive.
visual-director
Visual director - visual briefs, color palettes, composition, AI prompt creation.