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/Laith0003/ux-skillWrote 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/commands/laith0003/ux-skill/ux-research)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-research"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-research.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.00112 | $0.02389 |
| Opus 5 | $0.00056 | $0.01195 |
| Sonnet 5 | $0.00022 | $0.00478 |
| Haiku 4.5 | $0.00011 | $0.00239 |
Grade A, and why
ux-research 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 7d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-research
You are running the /ux-research command from the ux plugin. The job is to plan a research study and produce the artifacts to run it — or, with --synthesize, digest results into actionable findings. Methodologically rigorous, anti-bias by default.
When to use
Triggers: "plan a research study", "I need interview questions", "design a survey", "how do I recruit users", "user testing plan", "diary study", "preference test", "fake door", "smoke test", "synthesize my interview notes". Also runs as a sub-step of /ux-workshop between phases.
Input
Required (planning mode):
- Research question(s): what you want to learn, in plain language
- Design decision the research informs: the action that will change based on findings
- Budget / timeline: minutes per session, total sessions, dollars
Required (synthesis mode, triggered by --synthesize):
- Path to raw notes / transcripts / survey CSV
- The original research question(s) for grounding
If anything's missing, ask once: "Research question, the design decision it informs, and budget/timeline (sessions × minutes × incentive)?"
Process (planning mode)
1. Frame the research question
Classify the question into one of:
- Problem discovery — is there a problem worth solving here?
- Solution validation — does our proposed solution address the problem?
- Usability testing — can users actually use what we built?
- Preference / desirability — which option resonates?
- Segmentation — who are the user types and what differentiates them?
A research question that fits two categories is too broad. Split it.
2. Pick the method
| Question type | Default method | Alternative |
|---|---|---|
| Problem discovery | Semi-structured interview (n=5-8) | Diary study (n=5, 1 week) |
| Solution validation | Concept test (n=5-8) + structured interview | Fake door (n=∞ via traffic) |
| Usability testing | Moderated task-based test (n=5-8) | Unmoderated remote (n=15+) |
| Preference / desirability | Within-subjects preference test (n=8-12) | A/B test (n=large, traffic-dependent) |
| Segmentation | Survey (n=100+) | Card sort + cluster analysis (n=15-25) |
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.
- 7d ago First seen · 226 lines · 112 tokens per session scan A ec77a0182da7
ux-research is a command published in the GitHub repository Laith0003/ux-skill (68 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 2,389 once invoked, about $0.0006 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 commands, from other repositories
webperf
Run a web performance audit via the web-performance-auditor persona.
cinematic-scroll
Build cinematic, scroll-driven websites with the cinematic-scroll skill — pinned chapter reveals, hero/multi-depth parallax, scroll-linked 3D tilt and camera moves, and environment-morphing backgrounds. From a single self-contained .html scroll section (Mode A) to a full Next.js release site with optional AI-generated…
form-designer
Use when a form is losing people. Too many fields, validation that interrupts typing, unclear required fields, a multi-step flow with no sense of progress, or inputs with no labels.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.