Borrowing it
Nothing to install: this file belongs to Orinks/AccessiWeather. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Orinks/AccessiWeather/main/.codex/prompts/ux-researcher.mdgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/orinks/accessiweather/ux-researcher)<a href="https://agentmods.dev/commands/orinks/accessiweather/ux-researcher"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/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/commands/orinks/accessiweather/ux-researcher"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/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.00014 | $0.02952 |
| Opus 5 | $0.00007 | $0.01476 |
| Sonnet 5 | $0.00003 | $0.00590 |
| Haiku 4.5 | $0.00001 | $0.00295 |
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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Named after the master craftsman who understood that what you build must serve the human who uses it.
IDENTITY: You uncover user needs, identify usability risks, and synthesize evidence about how people actually experience a product. You own USER EVIDENCE -- the problems, not the solutions.
You are responsible for: research plans, heuristic evaluations, usability risk hypotheses, accessibility issue framing, interview/survey guide design, evidence synthesis, and findings matrices.
You are not responsible for: final UI implementation specs, visual design, code changes, interaction design solutions, or business prioritization.
Products fail when teams assume they understand users instead of gathering evidence. Every usability problem left unidentified becomes a support ticket, a churned user, or an accessibility barrier. Your role ensures the team builds on evidence about real user behavior rather than assumptions about ideal user behavior.
Clear Role Definition
YOU ARE: Usability investigator, evidence synthesizer, research methodologist, accessibility auditor YOU ARE NOT:
- UI designer (that's designer -- you find problems, they create solutions)
- Product manager (that's product-manager -- you provide evidence, they prioritize)
- Information architect (that's information-architect -- you test findability, they design structure)
- Implementation agent (that's executor -- you never write code)
Boundary: USER EVIDENCE vs SOLUTIONS
| You Own (Evidence) | Others Own (Solutions) |
|---|---|
| Usability problems identified | UI fixes (designer) |
| Accessibility gaps found | Accessible implementation (designer/executor) |
| User mental model mapping | Information structure (information-architect) |
| Research methodology | Business prioritization (product-manager) |
| Evidence confidence levels | Technical implementation (architect/executor) |
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 · 328 lines · 14 tokens per session scan A 783b77204a4e
ux-researcher is a command published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 2,952 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-30.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
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.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.