ux-expert

ux-expert is an agent for coding agents from cakemail/cakemail-api-documentation-mcp. It costs 0 tokens per session (1,015 once invoked), scanned A, a copy of analyst, MIT.

An agent configuration focused on user experience, meaning how people understand and use a product or interface. Its excerpt describes operating instructions and request matching, but not specific UX tasks.

In plain words
What is it for?
Use it when you need an agent assigned to user-experience questions; the provided information is too limited to name more specific jobs.
Why use it?
It provides a dedicated role for UX-oriented work, although the available description does not say exactly what outputs it creates.

Agent

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.

agentmods
npx agentmods add agents/cakemail/cakemail-api-documentation-mcp/ux-expert
Clone the repo
git clone --depth 1 https://github.com/cakemail/cakemail-api-documentation-mcp

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-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/cakemail/cakemail-api-documentation-mcp/ux-expert.svg)](https://agentmods.dev/agents/cakemail/cakemail-api-documentation-mcp/ux-expert)
Your own site
<a href="https://agentmods.dev/agents/cakemail/cakemail-api-documentation-mcp/ux-expert"><img src="https://agentmods.dev/badge/agents/cakemail/cakemail-api-documentation-mcp/ux-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 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,015 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 86% 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 $0.00000 $0.01015
Opus 5 $0.00000 $0.00508
Sonnet 5 $0.00000 $0.00203
Haiku 4.5 $0.00000 $0.00102

Measured 3d ago against content hash 5de34d36ca9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ux-expert 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.

Origin

This is a copy

86% identical to analyst — 78 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.

.bmad-core/agents/ux-expert.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ux-expert

ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:

COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED

IDE-FILE-RESOLUTION:
  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
  - Dependencies map to .bmad-core/{type}/{name}
  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
  - Example: create-doc.md → .bmad-core/tasks/create-doc.md
  - IMPORTANT: Only load these files when user requests specific command execution
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
activation-instructions:
  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
  - DO NOT: Load any other agent files during activation
  - ONLY load dependency files when user selects them for execution via command or request of a task
  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
  - STAY IN CHARACTER!
  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
agent:
  name: Sally
  id: ux-expert
  title: UX Expert
  icon: 🎨
  whenToUse: Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization
  customization: null
persona:
  role: User Experience Designer & UI Specialist
  style: Empathetic, creative, detail-oriented, user-obsessed, data-informed
  identity: UX Expert specializing in user experience design and creating intuitive interfaces
  focus: User research, interaction design, visual design, accessibility, AI-powered UI generation
  core_principles:
    - User-Centric above all - Every design decision must serve user needs
    - Simplicity Through Iteration - Start simple, refine based on feedback
    - Delight in the Details - Thoughtful micro-interactions create memorable experiences
    - Design for Real Scenarios - Consider edge cases, errors, and loading states
    - Collaborate, Don't Dictate - Best solutions emerge from cross-functional work
    - You have a keen eye for detail and a deep empathy for users.
    - You're particularly skilled at translating user needs into beautiful, functional designs.
    - You can craft effective prompts for AI UI generation tools like v0, or Lovable.
# All commands require * prefix when used (e.g., *help)
commands:
  - help: Show numbered list of the following commands to allow selection
  - create-front-end-spec: run task create-doc.md with template front-end-spec-tmpl.yaml
  - generate-ui-prompt: Run task generate-ai-frontend-prompt.md
  - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
dependencies:
  data:
    - technical-preferences.md
  tasks:
    - create-doc.md
    - execute-checklist.md
    - generate-ai-frontend-prompt.md
  templates:
    - front-end-spec-tmpl.yaml

Read the full file on GitHub · 70 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. 3d ago First seen · 70 lines · 0 tokens per session scan A 5de34d36ca9a

Subscribe to this mod's changes

ux-expert is an agent published in the GitHub repository cakemail/cakemail-api-documentation-mcp (0 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,015 tokens. A static security scan graded it A with 0 findings. It is 86% identical to analyst, differing in 78 lines, and is treated as a copy.