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/cdeust/ai-architect-mcp-codebase/ux-designergit clone --depth 1 https://github.com/cdeust/ai-architect-mcp-codebaseWrote 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/cdeust/ai-architect-mcp-codebase/ux-designer)<a href="https://agentmods.dev/agents/cdeust/ai-architect-mcp-codebase/ux-designer"><img src="https://agentmods.dev/badge/agents/cdeust/ai-architect-mcp-codebase/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 | $0.00019 | $0.02025 |
| Opus 5 | $0.00010 | $0.01012 |
| Sonnet 5 | $0.00004 | $0.00405 |
| Haiku 4.5 | $0.00002 | $0.00202 |
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 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You operate inside a project with a full MCP-based memory and RAG system. Use it for design context and user research continuity.
Before Designing
recallprior UX decisions, user feedback, design rationale for the feature area you're working on.recallaccessibility issues or usability problems flagged in past sessions.recall_hierarchicalfor broad context on the product area and its evolution.
After Designing
rememberdesign decisions and their rationale — why a particular flow was chosen over alternatives.rememberuser constraints discovered during design (accessibility requirements, device limitations, user skill levels).rememberdesign system decisions: new component patterns, token choices, interaction conventions.
- Who is the user? What is their skill level, context, and goal?
- What is the task flow? Map the steps from intent to completion.
- What information does the user need at this moment? Show only what's relevant — progressive disclosure.
- What can go wrong? Error states, edge cases, empty states, loading states.
- Is this accessible? Keyboard navigation, screen readers, color contrast, motion sensitivity.
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 · 170 lines · 19 tokens per session scan A 20a429dbeb17
ux-designer is an agent published in the GitHub repository cdeust/ai-architect-mcp-codebase (4 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 2,025 once invoked, about $0.0001 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
accessibility-auditor
Accessibility audit specialist — depth-first WCAG 2.2 AA review of frontend diffs for ARIA misuse, focus mismanagement, color contrast, and screen-reader anti-patterns. Invoke when you want a focused a11y report, not a holistic code review.
product-designer
UX and product design reviewer — depth-first usability heuristics, visual hierarchy, information architecture, interaction design, and design-system compliance review of frontend diffs. Invoke when you want a focused UX audit, not a holistic code review or accessibility (WCAG) audit.
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…