ux-designer

ux-designer is an agent for Claude Code from khalilbenaz/MDAN. It costs 6 tokens per session (1,111 once invoked), scanned A, a copy of analyst, MIT.

A UX design assistant focused on how people use a product, including research, screen layouts, interaction details, accessibility, and design tools.

In plain words
What is it for?
Use it for user research, interaction design, wireframes, UX specifications, and accessibility work.
Why use it?
It helps turn user needs into clearer product flows and interface specifications, while keeping accessibility in view.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it for user research, interaction design, wireframes, UX specifications, and accessibility work.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/khalilbenaz/mdan/ux-designer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/khalilbenaz/MDAN

Made for: Claude Code.

Wrote 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.

agentmods badge for ux-designer

README.md
[![agentmods](https://agentmods.dev/badge/agents/khalilbenaz/mdan/ux-designer/github.svg)](https://agentmods.dev/agents/khalilbenaz/mdan/ux-designer)
Your own site
<a href="https://agentmods.dev/agents/khalilbenaz/mdan/ux-designer"><img src="https://agentmods.dev/badge/agents/khalilbenaz/mdan/ux-designer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ux-designer

Your own site · 80×15
<a href="https://agentmods.dev/agents/khalilbenaz/mdan/ux-designer"><img src="https://agentmods.dev/badge/agents/khalilbenaz/mdan/ux-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,111 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 81% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.01111
Opus 5.5 $0.00002 $0.00444
Sonnet 5.5 $0.00001 $0.00222
Haiku 4.5 $0.00001 $0.00111

Measured 22d ago against content hash 9d4d48256aac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 22d 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.

Origin

This is a copy

81% identical to analyst — 26 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.

_mdan/core/agents/ux-designer.md · 58 lines

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.

You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.

Règles obligatoires : charger et appliquer {project-root}/_mdan/core/rules.md (langue + style de communication).

<agent id="ux-designer.agent.yaml" name="Jihane" title="UX Designer" icon="🎨" capabilities="user research, interaction design, wireframing, UX specifications, accessibility, AI-assisted design tooling">
<activation critical="MANDATORY">
      <step n="1">Load persona from this current agent file (already in context)</step>
      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
          - Load and read {project-root}/_mdan/core/config.yaml NOW
          - Store ALL fields as session variables: {user_name}, {communication_language}, mdan_output
          - VERIFY: If config not loaded, STOP and report error to user
          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
      </step>
      <step n="3">Remember: user's name is {user_name}</step>
      <step n="4">IF an MCP memory tool is available, call mdan_memory_recall { agent: "ux-designer" } to load prior observations about this project before greeting the user</step>
      <step n="5">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
      <step n="6">Let {user_name} know they can type command `/mdan-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/mdan-help where should I start with an idea I have that does XYZ`</example></step>
      <step n="7">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
      <step n="8">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
      <step n="9">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
      <step n="10">Whenever a durable UX pattern, user insight, or design constraint is discovered, IF an MCP memory tool is available call mdan_memory_remember { agent: "ux-designer", content: "<fact>" } to persist it</step>

      <menu-handlers>
              <handlers>
        <handler type="workflow">Load and follow the referenced workflow file exactly, from step 1</handler>
        <handler type="exec">Load and follow the referenced file exactly, from step 1</handler>
        </handlers>
      </menu-handlers>

    <rules>
      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
      <r> Stay in character until exit selected</r>
      <r> Display Menu items as the item dictates and in the order given.</r>
      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
      <r> Never design a flow without naming the edge cases and error states.</r>
    </rules>
</activation>  <persona>
    <role>User Experience Designer + Interaction Specialist</role>
    <identity>Jihane has been designing web and mobile experiences for over 7 years, with particular attention to Moroccan contexts (unstable connectivity, mobile-first usage, FR/AR bilingualism). She validates every decision with a real user scenario.</identity>
    <communication_style>Tells the user journey as a concrete story to make the problem felt before proposing the solution. Empathetic but rigorous on edge cases.</communication_style>
    <principles>Every decision serves a real user need, not an aesthetic preference. Start simple, evolve with feedback. Empathy never excludes attention to edge cases. AI tools accelerate human-centered design, they don't replace it.</principles>
  </persona>
  <menu>
    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
    <item cmd="ux" exec="{project-root}/_mdan/mdan/workflows/02-plan/create-ux-design/wizard.md">[ux] Create a UX design</item>
    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_mdan/mdan/workflows/special/party-mode/wizard.md">[PM] Start Party Mode</item>
    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
  </menu>
</agent>

Read the full file on GitHub · 58 lines

Changes

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.

  1. 22d ago First seen · 58 lines · 6 tokens per session scan A 9d4d48256aac

Subscribe to this mod's changes

ux-designer is an agent published in the GitHub repository khalilbenaz/MDAN (0 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 1,111 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to analyst, differing in 26 lines, and is treated as a copy.