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.
npx skills add hueyexe/frontend-agent-skills --skill ux-research-discovery-testinggit clone --depth 1 https://github.com/hueyexe/frontend-agent-skillsWrote 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/skills/hueyexe/frontend-agent-skills/ux-research-discovery-testing)<a href="https://agentmods.dev/skills/hueyexe/frontend-agent-skills/ux-research-discovery-testing"><img src="https://agentmods.dev/badge/skills/hueyexe/frontend-agent-skills/ux-research-discovery-testing/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/skills/hueyexe/frontend-agent-skills/ux-research-discovery-testing"><img src="https://agentmods.dev/badge/skills/hueyexe/frontend-agent-skills/ux-research-discovery-testing.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.00027 | $0.05152 |
| Opus 5 | $0.00014 | $0.02576 |
| Sonnet 5 | $0.00005 | $0.01030 |
| Haiku 4.5 | $0.00003 | $0.00515 |
Grade A, and why
ux-research-discovery-testing 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 11d 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 — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Research Discovery Testing
Purpose
Help an agent make better product, UX, UI, and frontend recommendations by grounding them in user goals, observed behavior, business outcomes, and testable evidence. Use this skill to choose just-enough research methods, write interview and usability-test plans, synthesize findings, identify opportunities, and explain evidence-backed product decisions.
It is an operating manual for doing practical research under real product constraints.
When to use this skill
Use this skill when the user asks you to:
- Plan discovery, customer interviews, field visits, contextual inquiry, or stakeholder interviews.
- Review, critique, redesign, or generate a UI where user behavior, task success, accessibility, or product outcomes matter.
- Create an interview guide, screener, usability-test script, research plan, synthesis framework, opportunity map, journey map, persona, task flow, or evidence-backed recommendation.
- Decide what to build, improve, remove, or test next.
- Evaluate a prototype, live UI, design system component, onboarding flow, form, navigation model, dashboard, empty state, error flow, or content hierarchy.
- Turn qualitative notes, analytics, survey findings, support tickets, screenshots, or observations into product decisions.
When not to use this skill
Do not use this skill as the primary tool when the task is only:
- Visual UI styling with no user goal, task, behavior, or product decision involved.
- Brand identity, illustration, or aesthetic exploration unrelated to use.
- Statistical analysis requiring rigorous sampling, inferential statistics, or experimental design beyond lightweight product research.
- Legal, medical, or regulated human-subjects research advice. In those cases, recommend qualified review and use only general UX planning guidance.
- Production frontend coding where the user has already specified the user problem, behavior, accessibility requirements, and interaction design.
Core principles
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 483 lines · 27 tokens per session scan A 1bf930dd0753
ux-research-discovery-testing is a skill published in the GitHub repository hueyexe/frontend-agent-skills (9 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 5,152 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-31.
Other skills, from other repositories
Accessibility Manual Audit
Teach agents to guide manual accessibility audits for keyboard, screen reader, zoom, reflow, focus, and WCAG 2.2 criteria that scanners miss.
interaction-design
Design meaningful interactions, microinteractions, animations, state machines, gesture patterns, error prevention, and product behavior. Specify how products respond to user input across all states and contexts using established interaction design principles.
ux-strategy
Connect design decisions to business outcomes through competitive analysis, opportunity mapping, Jobs to Be Done, outcome-driven discovery, value proposition design, and UX metrics. Shape product direction with strategic frameworks grounded in evidence.
design-ops
Run design sprints, manage handoff, establish team rituals, documentation standards, and design QA processes. Covers the operational side of design — how teams organize work, collaborate with engineering, and ship quality.
design-systems
Build, document, and maintain design systems with design tokens, component specifications, pattern libraries, naming conventions, and governance processes. Conduct system audits, define component hierarchies, and establish shared design languages.
mobile-analyzer
Mobile-specific UX analysis — touch interactions, viewport issues, scroll behavior, mobile vs desktop patterns, and responsive design validation. Use when investigating mobile experience, responsive design bugs, or mobile conversion rates.