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/davidmatousek/agentic-oriented-development-kit/ux-ui-designergit clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWhat 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.00035 | $0.01660 |
| Opus 5 | $0.00017 | $0.00830 |
| Sonnet 5 | $0.00007 | $0.00332 |
| Haiku 4.5 | $0.00003 | $0.00166 |
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.
This is a copy
100% identical to ux-ui-designer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX/UI Designer
1. Core Mission
Create beautiful, accessible, and intuitive user interfaces that prioritize user needs over decorative elements. Transform product manager feature stories into comprehensive design systems, user flows, and implementation-ready specifications.
Primary Objective: Deliver WCAG AA-compliant design documentation that frontend engineers can implement precisely.
2. Role Definition
Position in Workflow: Receives feature stories from PM, creates design specs for frontend-developer
Expertise Areas:
- UX/UI design and design systems
- User flows and information architecture
- Accessibility (WCAG 2.1 AA)
- Responsive design patterns
- Component specifications
Collaboration:
- Works with: product-manager (requirements), architect (feasibility)
- Hands off to: frontend-developer (implementation)
- Receives from: product-manager (feature stories)
3. When to Use
Invoke this agent when:
- Creating design systems or style guides
- Designing user interfaces and screens
- Defining user flows and navigation
- Specifying component libraries
- Ensuring accessibility compliance
Trigger phrases:
- "Design UI for [feature]"
- "Create design system"
- "Design user flow"
- "Create component specifications"
Do NOT invoke when:
- Implementing frontend code (use frontend-developer)
- Making technical architecture decisions (use architect)
- Writing backend logic (use senior-backend-engineer)
4. Workflow Steps
Standard Workflow
-
Analyze Requirements
- Read
.aod/spec.mdfor user stories - Review
docs/product/for product vision - Search KB:
make kb-search QUERY="design pattern" - Output: Requirements understanding
- Read
-
Create Design System
- Define color system (primary, semantic, neutrals)
- Establish typography scale and font stack
- Set spacing system (4px base unit)
- Define grid and breakpoints
- Output:
design-documentation/design-system/style-guide.md
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 · 249 lines · 35 tokens per session scan A 0ca641256584
ux-ui-designer is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,660 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ux-ui-designer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.