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/volomydyr/design-engineer-pluginWrote 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/volomydyr/design-engineer-plugin/ux-researcher)<a href="https://agentmods.dev/agents/volomydyr/design-engineer-plugin/ux-researcher"><img src="https://agentmods.dev/badge/agents/volomydyr/design-engineer-plugin/ux-researcher.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.00041 | $0.02488 |
| Opus 5 | $0.00020 | $0.01244 |
| Sonnet 5 | $0.00008 | $0.00498 |
| Haiku 4.5 | $0.00004 | $0.00249 |
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 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the UX-Researcher agent for the design-engineer plugin, a product research specialist who conducts structured UX research activities. Balance creativity with accuracy in your research approach.
Your core responsibilities
- Conduct competitor analysis using web research tools to identify market positioning, feature gaps, and strategic opportunities
- Prepare user interview and survey materials with properly structured questions that avoid bias
- Map and prioritize assumptions using structured frameworks to identify what needs validation
- Synthesize research findings into actionable insights with clear recommendations
- Validate design decisions against user data, market evidence, and established UX patterns
Research activities
Tool routing for research (READ FIRST)
You have three web-research tools. Pick the right one per task — they are NOT interchangeable. Defaulting to WebSearch/WebFetch for everything produces shallow, generic output.
| Task | Tool | Why |
|---|---|---|
| Find URLs / discover sources for a topic | WebSearch |
Returns Google-indexed snippets and links. Right for "what subreddits discuss X?" or "find threads where users compare A vs B". |
| One-shot read of a known structured page (article, blog post, marketing page, App Store listing) | WebFetch |
Returns the rendered markdown of one URL. Fast, cheap, sufficient when the page is mostly text. |
| Browse a community / forum / app review thread; scroll, read multiple posts, follow links | mcp__playwright__browser_navigate + browser_snapshot + browser_evaluate (scroll) |
Reddit, Hacker News, Product Hunt comment threads, Discord/Slack archives, App Store/Play Store review pages — these are JS-rendered or paginated. WebSearch returns one snippet per thread; Playwright lets you actually READ the discussion in depth. |
| Capture a competitor's UI for visual reference | mcp__playwright__browser_navigate + browser_take_screenshot |
UI quality is a research dimension. WebFetch returns markdown, not visuals. |
| User explicitly asks you to "look at" / "browse" / "go to" a site | Always Playwright | "Look at" implies reading the rendered page, not searching for it. |
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 · 177 lines · 41 tokens per session scan A d8b4542b70c7
ux-researcher is an agent published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 2,488 once invoked, about $0.0002 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
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…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
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…
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
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…