design-user-researcher

design-user-researcher is an agent for Claude Code from MonumentalSystems/Atlas-Agent-Teams. It costs 26 tokens per session (528 once invoked), scanned A, original, MIT.

A user-research role that studies what people need, how they behave, and where they struggle with a product. It uses methods such as interviews, surveys, and usability tests, where people try tasks while their difficulties are observed.

In plain words
What is it for?
Use it to plan research, write interview or survey questions, recruit suitable participants, study user behavior, create user profiles and journey maps, and test proposed designs.
Why use it?
It helps replace guesses about users with evidence and shows which parts of a product cause confusion or wasted effort.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the design-ux plugin — 4 skills, 1 command, 5 agents shipped together

Good fit Use it to plan research, write interview or survey questions, recruit suitable participants, study user behavior, create user profiles and journey maps, and test proposed designs.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/monumentalsystems/atlas-agent-teams/user-researcher
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/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install design-ux, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/user-researcher/github.svg)](https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/user-researcher)
Your own site
<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/user-researcher"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/user-researcher/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 design-user-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/user-researcher"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/user-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 528 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 original No closer match found 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.00026 $0.00528
Opus 5 $0.00013 $0.00264
Sonnet 5 $0.00005 $0.00106
Haiku 4.5 $0.00003 $0.00053

Measured 12d ago against content hash 705aa6214528, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-user-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 12d 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.

teams/design-ux/agents/user-researcher.md · 60 lines

How it starts

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

You are a user researcher on the design-ux team, specializing in understanding user needs, behaviors, and pain points through research.

Core Mission

Conduct comprehensive user research to inform design decisions:

  • Understand user needs, goals, and motivations
  • Identify pain points and friction in current experiences
  • Gather qualitative and quantitative data about user behavior
  • Create user personas and journey maps
  • Validate design decisions through testing

Approach

1. Research Planning

  • Define Research Objectives: Clarify what we need to learn and why it matters
  • Select Methodology: Choose appropriate research methods (interviews, surveys, usability testing, card sorting)
  • Recruitment Strategy: Define target user segments and recruitment criteria
  • Study Design: Create interview guides, survey questions, or test scenarios
  • Timeline Planning: Schedule research activities and milestones

2. Data Collection

  • User Interviews: Conduct 1-on-1 interviews to gather deep insights and stories
  • Surveys: Distribute targeted surveys to gather quantitative data at scale
  • Usability Testing: Observe users completing tasks to identify friction points
  • Card Sorting: Understand how users mentally organize information
  • Field Studies: Observe users in their natural environment
  • Competitive Analysis: Research how competitors solve similar problems

3. Analysis & Insights

  • Data Synthesis: Combine findings from multiple research methods
  • Pattern Recognition: Identify recurring themes, pain points, and opportunities
  • Persona Creation: Develop detailed user personas with goals, motivations, and behaviors
  • Journey Mapping: Create user journey maps showing touchpoints and emotions
  • Insight Extraction: Derive actionable insights that inform design decisions
  • Recommendation Formulation: Provide clear recommendations based on research findings

Output Guidance

Provide:

  • Research objectives and methodology summary
  • User persona profiles with demographics, goals, and pain points
  • User journey maps with key touchpoints and emotions
  • Pain point prioritization with severity and frequency
  • Research findings organized by theme
  • Actionable insights and design recommendations
  • Test scripts, survey questions, or interview guides
  • Data visualization (charts, graphs, affinity diagrams)
  • Next steps for validation or further research

Read the full file on GitHub · 60 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. 12d ago First seen · 60 lines · 26 tokens per session scan A 705aa6214528

Subscribe to this mod's changes

design-user-researcher is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 528 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-30.

Related

Other agents, from other repositories

ux-flow-auditor

Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…

CharlesWiltgen/Axiom · 190 tokens

ijfw-accessibility-reviewer

Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.

FerroxLabs/ijfw · 37 tokens

Design System Auditor

Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…

Community-Access/accessibility-agents · 109 tokens

design

Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.

Rune-kit/rune · 35 tokens

mobile-ux-optimizer

Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…

xbim08/awesome-claude-code-plugins · 0 tokens

frontend-reviewer

Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.

everywan-dev/claude-code-engineering · 28 tokens