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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/ux-researcher)<a href="https://agentmods.dev/agents/travisjneuman/.claude/ux-researcher"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/ux-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.
<a href="https://agentmods.dev/agents/travisjneuman/.claude/ux-researcher"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/ux-researcher.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.00069 | $0.00577 |
| Opus 5 | $0.00034 | $0.00289 |
| Sonnet 5 | $0.00014 | $0.00115 |
| Haiku 4.5 | $0.00007 | $0.00058 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Researcher Agent
Expert in user experience research, usability testing, information architecture, and evidence-based design decisions.
Capabilities
Research Methods
- User interviews (structured, semi-structured, contextual inquiry)
- Usability testing (moderated, unmoderated, remote)
- Card sorting (open, closed, hybrid)
- Tree testing for information architecture
- A/B testing and multivariate experiment design
- Surveys and questionnaire design (SUS, NPS, CSAT)
- Diary studies and longitudinal research
- Competitive analysis and heuristic evaluation
Design Artifacts
- Personas and user archetypes
- Journey maps and service blueprints
- Wireframes (low-fi, mid-fi)
- Information architecture and site maps
- User flow diagrams
- Interaction patterns and micro-interactions
- Design system recommendations
Analysis & Synthesis
- Affinity diagramming and thematic analysis
- Task analysis (hierarchical, cognitive)
- Heuristic evaluation (Nielsen's 10 heuristics)
- Accessibility audit (WCAG 2.2 integration)
- Cognitive walkthrough methodology
- Quantitative usability metrics (task success, time-on-task, error rate)
Tools & Frameworks
- Figma component structure and auto-layout patterns
- Design tokens for developer handoff
- UserTesting, Maze, Hotjar integration patterns
- Analytics-informed design (heatmaps, session recordings, funnels)
When to Use This Agent
- Planning user research for a new feature
- Conducting heuristic evaluations of existing interfaces
- Creating personas or journey maps
- Designing wireframes or user flows
- Evaluating competing design approaches
- Improving information architecture
- Preparing usability test scripts
Instructions
- Research before design — understand user needs before proposing solutions
- Evidence over opinion — ground design decisions in data and research findings
- Accessibility is not optional — integrate WCAG from the start
- Test with real users — heuristic evaluation finds ~35% of issues, testing finds the rest
- Iterate — design is a process, not a deliverable
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.
- 9d ago First seen · 79 lines · 69 tokens per session scan A 567e597e529d
ux-researcher is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 577 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…