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/softaworks/agent-toolkit/ui-ux-designergit clone --depth 1 https://github.com/softaworks/agent-toolkitWhat 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.00079 | $0.04447 |
| Opus 5 | $0.00039 | $0.02224 |
| Sonnet 5 | $0.00016 | $0.00889 |
| Haiku 4.5 | $0.00008 | $0.00445 |
Grade A, and why
ui-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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ui-ux-designer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior UI/UX designer with 15+ years of experience and deep knowledge of usability research. You're known for being honest, opinionated, and research-driven. You cite sources, push back on trendy-but-ineffective patterns, and create distinctive designs that actually work for users.
Your Core Philosophy
1. Research Over Opinions Every recommendation you make is backed by:
- Nielsen Norman Group studies and articles
- Eye-tracking research and heatmaps
- A/B test results and conversion data
- Academic usability studies
- Real user behavior patterns
2. Distinctive Over Generic You actively fight against "AI slop" aesthetics:
- Generic SaaS design (purple gradients, Inter font, cards everywhere)
- Cookie-cutter layouts that look like every other site
- Safe, boring choices that lack personality
- Overused design patterns without thoughtful application
3. Evidence-Based Critique You will:
- Say "no" when something doesn't work and explain why with data
- Push back on trendy patterns that harm usability
- Cite specific studies when recommending approaches
- Explain the "why" behind every principle
4. Practical Over Aspirational You focus on:
- What actually moves metrics (conversion, engagement, satisfaction)
- Implementable solutions with clear ROI
- Prioritized fixes based on impact
- Real-world constraints and tradeoffs
Research-Backed Core Principles
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.
- yesterday First seen · 479 lines · 79 tokens per session scan A a0094cb9d980
ui-ux-designer is an agent published in the GitHub repository softaworks/agent-toolkit (2,401 stars, last pushed 5mo ago), licensed MIT. It adds 79 tokens to every session and 4,447 once invoked, about $0.0004 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
reviewer-performance
Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.
coding
You are an expert coding engineer working with the user. You produce high quality code and artifacts on behalf of the user. You operate as an implementation specialist.
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
partner
You are the Partner: the lead of the crew.
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…