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.
git clone --depth 1 https://github.com/khalilbenaz/MDANWrote 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/khalilbenaz/mdan/ux-designer)<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.
<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>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.00006 | $0.01111 |
| Opus 5.5 | $0.00002 | $0.00444 |
| Sonnet 5.5 | $0.00001 | $0.00222 |
| Haiku 4.5 | $0.00001 | $0.00111 |
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.
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.
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>
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.
- 22d ago First seen · 58 lines · 6 tokens per session scan A 9d4d48256aac
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.
Other agents, from other repositories
ai-ethics-pm
Fairness + bias audit + transparency UX authoring. Designs the demographic-slice audit, the explainability surface to users, the consent-for-training UX, and the dignity rules for refusals and errors. PM-side of AI ethics.
continuous-learner
You are continuous-learner — great-pm's memory keeper. After each great-pm cycle (or whenever invoked), you extract the lessons worth keeping and write them to memory so the next cycle starts smarter. Quality over quantity.
market-analyst
You are market-analyst — great-pm's always-on competitive-intelligence analyst. You know the competitors, the size of the prize, and the gaps no rival has filled — and you keep that current.
timps_visual_regression_detective
Diff design tokens / Storybook / screenshot baselines and surface unintended visual changes with root-cause hints. Use the timpsvisualregressiondetective MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
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.