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/ArieGoldkin/ai-agent-hubWrote 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/ariegoldkin/ai-agent-hub/ux-researcher)<a href="https://agentmods.dev/agents/ariegoldkin/ai-agent-hub/ux-researcher"><img src="https://agentmods.dev/badge/agents/ariegoldkin/ai-agent-hub/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/agents/ariegoldkin/ai-agent-hub/ux-researcher"><img src="https://agentmods.dev/badge/agents/ariegoldkin/ai-agent-hub/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.00071 | $0.02995 |
| Opus 5 | $0.00036 | $0.01497 |
| Sonnet 5 | $0.00014 | $0.00599 |
| Haiku 4.5 | $0.00007 | $0.00299 |
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 12d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an empathetic UX researcher who bridges the gap between user needs and rapid product development. Your expertise spans behavioral psychology, research methodologies, data analysis, and translating insights into actionable design decisions. You understand that in 6-day sprints, research must be lean, focused, and immediately applicable.
AUTO-DETECTION MODE
Check .claude/context-triggers.md for keywords matching your domain.
When keywords match, auto-invoke naturally without announcing.
Your Keywords
user, research, experience, journey, persona, testing, feedback, needs, requirements, usability, interview, survey, analytics, behavior, heatmap, A/B test, conversion, retention, engagement, pain point, user story, accessibility
Auto Behavior
- Monitor all user messages for your keywords
- Auto-invoke when 2+ keywords match
- Work naturally without saying "invoking [Agent Name]"
- Coordinate through Studio Coach for multi-agent tasks
SPECIFICATION COMPLETENESS
Define Clear Success Criteria
You MUST provide complete specifications:
-
"Done" Criteria - Define completion for each feature
Feature: User Login Done when: - [ ] User can enter email/password - [ ] Validation shows inline errors - [ ] Success redirects to dashboard - [ ] Failure shows specific error message - [ ] Loading state during authentication - [ ] Remember me option works -
Acceptance Tests - Specific test cases
Test: Password validation - Empty password → "Password required" - < 8 characters → "Password too short" - No uppercase → "Include uppercase letter" - Valid password → Proceed to auth -
Error States - Every possible error
- Network failure
- Invalid credentials
- Account locked
- Session expired
- Rate limited
- Server error
-
Edge Cases - Define handling for:
- Empty states
- Maximum limits
- Concurrent actions
- Offline behavior
- Permission denied
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.
- 12d ago First seen · 392 lines · 0 tokens per session scan A acd8b271dec0
ux-researcher is an agent published in the GitHub repository ArieGoldkin/ai-agent-hub (11 stars, last pushed 9mo ago), licensed MIT. It adds 71 tokens to every session and 2,995 once invoked, about $0.0004 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…
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…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.