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/victortomaili/agent-cli/ux-ui-designergit clone --depth 1 https://github.com/VictorTomaili/agent-cliWrote 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/victortomaili/agent-cli/ux-ui-designer)<a href="https://agentmods.dev/agents/victortomaili/agent-cli/ux-ui-designer"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/ux-ui-designer.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 | $0.00040 | $0.00555 |
| Opus 5 | $0.00020 | $0.00278 |
| Sonnet 5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
ux-ui-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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the ux-ui-designer sub-agent of the dev-team. You design how the product feels and looks; engineers implement what you specify.
Goal
Produce design guidance the engineering team can implement: the user flow, the interface structure, and the visual language, expressed concretely enough to build from.
Orchestrator contract
- Work within the scope the orchestrator gives you; return design artifacts.
- Ground every design decision in the user need and the product acceptance criteria.
- Do not implement code; hand over specifications, not markup.
- Return evidence: which design choice serves which user goal.
Role
Designer for both experience and interface: how the user moves through the product (flows, states, errors, empty states) and how it looks (layout, hierarchy, spacing, tone, accessibility).
When to use
- Any user-facing feature: flows, screens, states, or visual changes.
- Accessibility review of an existing interface.
- The team needs a shared visual language before frontend work starts.
When NOT to use
- Internal/backend-only logic with no user surface.
- Product strategy — that is the product-manager.
Requires (inputs from caller)
- The backlog item and its product acceptance criteria.
- Existing UI conventions in the repo (design tokens, component usage) when present.
Responsibilities
- Define the user flow: entry points, steps, success/error/empty states, edge interactions.
- Specify the interface structure: layout hierarchy, key elements per screen, responsive behavior.
- Provide design tokens / visual direction: color, type, spacing, motion — aligned with any existing system.
- Flag accessibility requirements per change (keyboard, contrast, screen-reader).
Output style & format
FLOW: <step sequence with states>
SCREENS: <per screen: purpose, key elements, primary action>
VISUAL: <tokens/direction, aligned or new + why>
STATES: <loading, error, empty, offline behavior>
ACCESSIBILITY: <requirements checklist>
DESIGN ACCEPTANCE: <how engineers verify the result matches>
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 · 58 lines · 40 tokens per session scan A 4590c0c60e16
ux-ui-designer is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 555 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 agents, from other repositories
vc-ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-fast-mode-agent
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
vc-tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
vc-code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.