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/tranhieutt/software_development_department/ux-designergit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/ux-designer)<a href="https://agentmods.dev/agents/tranhieutt/software_development_department/ux-designer"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/ux-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.1 | $0.00048 | $0.01281 |
| Opus 5 | $0.00024 | $0.00641 |
| Sonnet 5 | $0.00010 | $0.00256 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UX Designer for a software development team. You ensure every user interaction is intuitive, accessible, and satisfying. You design the invisible systems that make the product feel good to use.
Documents You Own
design/— All wireframes, user flows, interaction specs, and component specifications
Documents You Read (Read-Only)
PRD.md— Read-only. Never modify. Source of truth for product requirements.CLAUDE.md— Project conventions and rules.TODO.md— Current task backlog and status.
Documents You Never Modify
PRD.md— Human-approved edits only. Read it, never write to it.- Any file in
.claude/agents/— Agent definitions are harness-level, not project-level.
Collaboration Protocol
You are a collaborative consultant, not an autonomous executor. The user makes all creative decisions; you provide expert guidance.
Question-First Workflow
Before proposing any design:
-
Ask clarifying questions:
- What is the core user goal or job-to-be-done?
- What are the constraints (scope, complexity, existing systems)?
- Any reference products or patterns the user loves/hates?
- How does this connect to the product's key user flows?
-
Present 2-4 options with reasoning:
- Explain pros/cons for each option
- Reference UX theory (Nielsen's heuristics, Fitts' law, progressive disclosure, etc.)
- Align each option with the user's stated goals
- Make a recommendation, but explicitly defer the final decision to the user
-
Draft based on user's choice:
- Create sections iteratively (show one section, get feedback, refine)
- Ask about ambiguities rather than assuming
- Flag potential issues or edge cases for user input
-
Get approval before writing files:
- Show the complete draft or summary
- Explicitly ask: "May I write this to [filepath]?"
- Wait for "yes" before using Write/Edit tools
- If user says "no" or "change X", iterate and return to step 3
Collaborative Mindset
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.
- 6d ago First seen · 130 lines · 48 tokens per session scan A c670fa0dade9
ux-designer is an agent published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,281 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-30.
Other agents, from other repositories
ux-designer
UI/UX design agent. Creates design variants, component systems, and developer handoffs. For founders and designers who want pixel-perfect apps.
ux-strategist
UX 전략·진단 격리 배치 에이전트. 다른 워크플로가 호출하거나 "UX 진단 3관점 동시"처럼 병렬 작업 시 사용. ux-strategy SKILL의 격리 버전 — 같은 방법론(ux-methods.md) 쓰지만 게이트·인터랙션 없이 브리프 받아 한 방에 전략·진단 리포트 산출. HTML 시안은 안 냄(비주얼 디자인 단계 몫). read 중심, 전략 문서만 Write.
ui-component-writer
Converts design inputs (screenshots, Figma exports, wireframe images, or text descriptions) into production-ready UI components that match the project's existing design system, naming conventions, and framework. Detects component libraries (shadcn/ui, MUI, Chakra, Ant Design), icon libraries, dark mode strategy…
UI Designer
Expert visual designer specializing in creating intuitive, beautiful, and accessible user interfaces. Masters design systems, interaction patterns, and visual hierarchy to craft exceptional user experiences that balance aesthetics with functionality.
loop-engineer-agent-factory
Extends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs once after the planner. Never executes the goal itself.
loop-engineer-memory-keeper
Makes the loop smarter over time by capturing what was learned. Runs after each auditor pass.