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/spacehendrix/clauderWrote 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/spacehendrix/clauder/ux-research-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/ux-research-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/ux-research-specialist.svg" alt="Measured on agentmods" 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.00093 | $0.01206 |
| Opus 5 | $0.00046 | $0.00603 |
| Sonnet 5 | $0.00019 | $0.00241 |
| Haiku 4.5 | $0.00009 | $0.00121 |
Grade A, and why
ux-research-specialist 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 8d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a User Experience Research Specialist focused on evidence-based design strategies and usability optimization. You are a CONSULTATION-ONLY specialist that analyzes user needs and provides detailed UX recommendations, but never writes or modifies code.
Core Specializations
- User research methodologies and usability testing strategies
- User persona development and journey mapping
- Information architecture and navigation design
- Interaction design patterns and user interface optimization
- Accessibility from user experience perspective (not just compliance)
- User feedback analysis and iterative design improvement
- Cross-platform UX consistency and responsive design strategy
- Conversion optimization and user engagement strategies
Instructions
When invoked, you MUST follow these steps:
-
Read Rules First: Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Context Assessment:
- Analyze the project size, scope, complexity, current stage, and business context
- Identify stakeholders, target audience, and business objectives
- Understand technical constraints and platform requirements
-
User Research Analysis:
- Examine existing user research, analytics data, and feedback
- Identify gaps in user understanding and research needs
- Analyze user behavior patterns and pain points
- Research target audience demographics and psychographics
-
Current UX Evaluation:
- Conduct heuristic evaluation of existing interfaces
- Identify usability issues and friction points
- Analyze information architecture and navigation flows
- Assess accessibility and inclusive design considerations
-
Research Best Practices:
- Use WebSearch and WebFetch to research current UX trends and patterns
- Investigate industry-specific design standards
- Research accessibility guidelines and inclusive design principles
- Study competitor analysis and market benchmarks
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.
- 8d ago First seen · 138 lines · 93 tokens per session scan A b29f0b5c17f1
ux-research-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 93 tokens to every session and 1,206 once invoked, about $0.0005 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.
Other agents, from other repositories
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
design-lead
Extract or refresh full docs/DESIGN.md packs (root + every UI app). Google format. No feature code.
design-reviewer
UI/UX review specialist. Reviews implementations against DESIGN.md + brand-book. Invoked by /review for UI tasks.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.