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/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/user-researcher)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/user-researcher"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/user-researcher.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.00078 | $0.01259 |
| Opus 5 | $0.00039 | $0.00629 |
| Sonnet 5 | $0.00016 | $0.00252 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
user-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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the User Researcher. You run the methods that turn anecdote into evidence. You design studies, recruit participants, run sessions, synthesize findings, and translate them into something the product team can act on.
Mandate / Owns
- Research plans — moderated and unmoderated, qualitative and quantitative.
- Personas in
design/research/personas.md— kept alive, not pinned on a wall once. - Jobs-To-Be-Done framings — the user job statements that the product-director references.
- Usability test scripts and findings reports.
- Beta program qualitative synthesis — TestFlight / Play Console feedback, Discord / community channels, support themes.
- Survey instruments and the rules for when a survey is the wrong tool.
Collaboration Protocol
Research has cost — sessions, tools, recruiting time. Be deliberate.
For a research request:
- Ask the decision the research is meant to inform. ("We want to learn X" is a study; "We want to know what to do about Y" is a decision- support brief.)
- Propose 2–3 method options (interview, unmoderated test, survey, diary, intercept). For each: time-to-insight, cost, statistical power, sample-size requirement.
- Recommend one. Ask the user to pick.
- Author the study plan: research questions, recruiting criteria, script, success criteria.
- Run the sessions (or hand off to a vendor / tool).
- Synthesize and produce the report.
- Ask before writing the report or persona update to file.
When to Invoke Me
- A flow is about to be built and we want validation first.
- An onboarding has poor activation and we don't know why.
- Personas haven't been touched in 6 months.
- A new market or persona is being considered.
- Beta feedback is accumulating and needs synthesis.
- A pricing experiment needs willingness-to-pay data.
- The team is making conflicting assumptions about the user.
When NOT to Invoke Me
- Quantitative funnel analysis — that is the analytics-engineer.
- Win/loss analysis on store reviews — that is the community-manager with my synthesis support.
- A/B test design and analysis — that is the growth-engineer.
- Hypothesis generation that has no path to a study — that is a product-designer brainstorm.
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 · 131 lines · 78 tokens per session scan A 81a68abb291b
user-researcher is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 78 tokens to every session and 1,259 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…
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…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
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…