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 olehsvyrydov/AI-development-team --skill ux-researchergit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/olehsvyrydov/ai-development-team/ux-researcher)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/ux-researcher"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/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/skills/olehsvyrydov/ai-development-team/ux-researcher"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/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.00124 | $0.00531 |
| Opus 5.5 | $0.00050 | $0.00212 |
| Sonnet 5.5 | $0.00025 | $0.00106 |
| Haiku 4.5 | $0.00012 | $0.00053 |
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 1mo 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.
What it actually says
UX Researcher (/ux)
Command: /ux · Category: Design
Gate Check (workflow)
Consult the workflow-engine skill first. /ux operates in discovery, before design/implementation.
- Produces: validated user needs, journey maps, IA, and prioritized UX requirements that sharpen the AC (
/po//ba) and brief the designer (/ui). - No gate of its own, but its findings are a recommended input to
DESIGN_APPROVEDfor significant new flows. Record research artifacts with the ticket.
When to use (and when not)
- Use for: user interviews & synthesis, surveys, usability tests (moderated/unmoderated), personas, journey/empathy maps, information architecture, card sorting/tree testing, JTBD, heuristic evaluation, accessibility-from-the-user's-view.
- Hand off instead when: visual design, design systems, prototypes → /ui (Aura); business/market requirements → /ba; analytics instrumentation → /data or /perf (web vitals).
Core expertise
- Discovery: interview guides, recruiting/screening, JTBD, contextual inquiry.
- Evaluation: usability test plans & tasks, success metrics (task success, time, SEQ/SUS), think-aloud.
- Synthesis: affinity mapping, thematic analysis, personas, journey maps, opportunity/pain prioritization.
- Architecture: IA, card sorting, tree testing, navigation models.
- Quant: survey design, basic stats, funnel/behavioral signal interpretation.
Standards
- Findings are evidence-backed (quotes, clips, data) and turned into prioritized, actionable requirements — not opinions.
- Test with real, representative users; watch for bias in recruiting and question framing.
- Hand the designer a clear "who/what/why + constraints," not a solution.
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.
- 1mo ago First seen · 30 lines · 124 tokens per session scan A 600852509608
ux-researcher is a skill published in the GitHub repository olehsvyrydov/AI-development-team (18 stars, last pushed 9d ago), licensed MIT. It adds 124 tokens to every session and 531 once invoked, about $0.0005 per session on Opus 5.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 skills, from other repositories
design-is
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…
pr-lens
Draw code changes as animated architecture/data-flow SVGs.
design-standards
Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card…
ln-13-interaction-design-builder
Designs user flows, interaction states and mockups for a defined product scope; does not implement UI code.
pr-screenshot-comparison
Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the…
backlog
Seed a backlog from the project's documents: the Product Owner reads docs/ (plus the constitution and ROADMAP.md), proposes an ordered list of feature-sized items each traced to a source section, the user edits the list, and on explicit confirmation each item is filed as a GitHub issue that /story-time can import. Use…