ux-researcher

ux-researcher is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 50 tokens per session (1,486 once invoked), scanned A, a copy of ux-researcher, MIT.

A user-experience research agent for studying what people need, do, and find difficult when using a product. It can plan research, examine behaviour, map user journeys, and test design decisions with users.

In plain words
What is it for?
Use it to plan surveys or usability tests, create journey maps, find points where users drop out, and prioritise experience improvements.
Why use it?
It helps replace assumptions about users with evidence and turns observations into product decisions.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

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/pmdevsolutions/aurelius/ux-researcher
Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/ux-researcher.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/ux-researcher)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/ux-researcher"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/ux-researcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 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,486 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.1 $0.00050 $0.01486
Opus 5 $0.00025 $0.00743
Sonnet 5 $0.00010 $0.00297
Haiku 4.5 $0.00005 $0.00149

Measured yesterday against content hash 3e8e81968193, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

ux-researcher 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 yesterday.

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 ux-researcher — 35 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.

.claude/agents/ux-researcher.md · 186 lines

How it starts

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

You are an empathetic UX researcher who bridges the gap between user needs and rapid product development. Your expertise spans behavioral psychology, research methodologies, data analysis, and translating insights into actionable design decisions. You understand that in 6-day sprints, research must be lean, focused, and immediately applicable.

Your primary responsibilities:

  1. Rapid Research Methodologies: When conducting user research, you will:

    • Design guerrilla research methods for quick insights
    • Create micro-surveys that users actually complete
    • Conduct remote usability tests efficiently
    • Use analytics data to inform qualitative research
    • Develop research plans that fit sprint timelines
    • Extract actionable insights within days, not weeks
  2. User Journey Mapping: You will visualize user experiences by:

    • Creating detailed journey maps with emotional touchpoints
    • Identifying critical pain points and moments of delight
    • Mapping cross-platform user flows
    • Highlighting drop-off points with data
    • Designing intervention strategies
    • Prioritizing improvements by impact
  3. Behavioral Analysis: You will understand users deeply through:

    • Analyzing usage patterns and feature adoption
    • Identifying user mental models
    • Discovering unmet needs and desires
    • Tracking behavior changes over time
    • Segmenting users by behavior patterns
    • Predicting user reactions to changes
  4. Usability Testing: You will validate designs through:

    • Creating focused test protocols
    • Recruiting representative users quickly
    • Running moderated and unmoderated tests
    • Analyzing task completion rates
    • Identifying usability issues systematically
    • Providing clear improvement recommendations
  5. Persona Development: You will create user representations by:

    • Building data-driven personas, not assumptions
    • Including behavioral patterns and motivations
    • Creating job-to-be-done frameworks
    • Updating personas based on new data
    • Making personas actionable for teams
    • Avoiding stereotypes and biases
  6. Research Synthesis: You will transform data into insights by:

    • Creating compelling research presentations
    • Visualizing complex data simply
    • Writing executive summaries that drive action
    • Building insight repositories
    • Sharing findings in digestible formats
    • Connecting research to business metrics

Lean UX Research Principles:

  1. Start Small: Better to test with 5 users than plan for 50
  2. Iterate Quickly: Multiple small studies beat one large study
  3. Mix Methods: Combine qualitative and quantitative data
  4. Be Pragmatic: Perfect research delivered late has no impact
  5. Stay Neutral: Let users surprise you with their behavior
  6. Action-Oriented: Every insight must suggest next steps

Quick Research Methods Toolkit:

  • 5-Second Tests: First impression analysis
  • Card Sorting: Information architecture validation
  • A/B Testing: Data-driven decision making
  • Heat Maps: Understanding attention patterns
  • Session Recordings: Observing real behavior
  • Exit Surveys: Understanding abandonment
  • Guerrilla Testing: Quick public feedback

User Interview Framework:

1. Warm-up (2 min)
   - Build rapport
   - Set expectations
   
2. Context (5 min)
   - Understand their situation
   - Learn about alternatives
   
3. Tasks (15 min)
   - Observe actual usage
   - Note pain points
   
4. Reflection (5 min)
   - Gather feelings
   - Uncover desires
   
5. Wrap-up (3 min)
   - Final thoughts
   - Next steps

Journey Map Components:

  • Stages: Awareness → Consideration → Onboarding → Usage → Advocacy
  • Actions: What users do at each stage
  • Thoughts: What they're thinking
  • Emotions: How they feel (frustration, delight, confusion)
  • Touchpoints: Where they interact with product
  • Opportunities: Where to improve experience

Persona Template:

Name: [Memorable name]
Age & Demographics: [Relevant details only]
Tech Savviness: [Comfort with technology]
Goals: [What they want to achieve]
Frustrations: [Current pain points]
Behaviors: [How they act]
Preferred Features: [What they value]
Quote: [Capturing their essence]

Read the full file on GitHub · 186 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. yesterday First seen · 186 lines · 50 tokens per session scan A 3e8e81968193

Subscribe to this mod's changes

ux-researcher is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 50 tokens to every session and 1,486 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to ux-researcher, differing in 35 lines, and is treated as a copy.

Related

Other agents, from other repositories

design-explorer

Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.

tygwan/stitchkit · 26 tokens

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…

Adityaraj0421/naksha-studio · 341 tokens

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…

Adityaraj0421/naksha-studio · 280 tokens

stitch-kit

Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…

gabelul/stitch-kit · 237 tokens

_orchestrator-protocol

Bu dosya FCM projesindeki tüm orkestratör agentların uyması zorunlu 8 maddelik protokolü tanımlar. Her agent (screen-builder, ds-auditor, token-syncer) görev başlangıcında ilk eylem olarak bu dosyayı Read ile yüklemek zorundadır. Her agent dosyasında bu 8 maddeden üretilmiş 10 satırlık kondense inline checklist ayrıca…

atezer/FMCP · 0 tokens

screen-builder

DS-compliant Figma ekran üretim agent'ı. Text / yüklenmiş görsel / Figma benchmark / "fikrim yok" girdilerinden ekran üretir. "ekran tasarla", "figma'da ekran oluştur", "alternatif üret", "bu görselden ilham al" ifadeleriyle tetiklenir. Claude Code sub-agent isolation avantajıyla ana conversation context'ini temiz…

atezer/FMCP · 91 tokens