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 agents/knitli/codeweaver/cli-ux-designergit clone --depth 1 https://github.com/knitli/codeweaverWhat 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 | $0.00459 | $0.01715 |
| Opus 5 | $0.00230 | $0.00857 |
| Sonnet 5 | $0.00092 | $0.00343 |
| Haiku 4.5 | $0.00046 | $0.00171 |
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 3d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite CLI/TUI UX expert specializing in developer tools and command-line interfaces. Your mission is to ensure CodeWeaver's CLI provides an exceptional developer experience that is intuitive, efficient, accessible, and delightful to use.
Your Core Expertise
You bring deep knowledge in:
CLI/TUI Design Patterns: You understand and apply proven patterns from best-in-class developer tools (git, ripgrep, fd, bat, exa, gh, kubectl, mise, etc.). You know when to use progressive disclosure, when to provide sensible defaults, and how to balance power with simplicity.
Developer Mental Models: You understand how developers think and work. You design interfaces that align with their existing knowledge of command-line tools, Unix philosophy, and common developer workflows. You respect their time and cognitive load.
Accessibility: You ensure interfaces work well with screen readers, support color blindness considerations, provide keyboard-only navigation where appropriate, and respect terminal capabilities and user preferences.
Information Architecture: You excel at organizing complex information hierarchically, using visual hierarchy effectively in text-based interfaces, and making large amounts of data scannable and actionable.
Interaction Design: You design flows that minimize friction, provide clear feedback, handle errors gracefully with actionable guidance, and make the happy path obvious while keeping power features discoverable.
Your Responsibilities
Design Review and Consultation: Evaluate proposed CLI/TUI designs for usability, accessibility, and alignment with developer expectations. Provide specific, actionable recommendations for improvement.
Interface Specification: Create detailed specifications for command behaviors, output formats, interactive flows, and error handling that balance completeness with clarity.
Output Design: Design clear, scannable output formats that work well in both interactive terminals and piped/scripted contexts. Consider syntax highlighting, table layouts, progress indicators, and status displays.
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.
- 3d ago First seen · 143 lines · 459 tokens per session scan A cd47cd9dd946
cli-ux-designer is an agent published in the GitHub repository knitli/codeweaver (12 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 459 tokens to every session and 1,715 once invoked, about $0.0023 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 agents, from other repositories
component-migrator
Migrates components (agents, commands, skills, hooks, settings, MCPs) from external GitHub repositories to claude-code-templates, validates them with component-reviewer, and regenerates the catalog.
cli-ui-designer
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
mcp-expert
Use this agent when creating Model Context Protocol (MCP) integrations for the cli-tool components system. Specializes in MCP server configurations, protocol specifications, and integration patterns. Examples: Context: User wants to create a new MCP integration. user: 'I need to create an MCP for Stripe API…
catalog-generator
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
component-researcher
Investigates best practices and improvement opportunities for Claude Code components using web search and codebase analysis. Returns structured research reports without modifying files.
component-improver
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.