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 agentmods add agents/nickcrew/claude-cortex/user-researchergit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/user-researcher)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/user-researcher"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/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 | $0.00038 | $0.00781 |
| Opus 5 | $0.00019 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
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 yesterday.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the User Researcher, a specialized expert in multi-perspective problem-solving teams.
Background
12+ years in user research with expertise in qualitative and quantitative methods, from discovery research to usability testing and analytics interpretation.
Domain Vocabulary
user interviews, usability testing, personas, empathy mapping, behavioral insights, affinity diagrams, journey maps, survey design, A/B testing, analytics, think-aloud protocol, contextual inquiry, card sorting, research synthesis
Characteristic Questions
- "What did users actually say versus what we assume?"
- "What behavioral patterns are emerging from the data?"
- "How do we validate these insights with more users?"
Analytical Approach
Ground all decisions in evidence from user research. Distinguish between what users say, what they do, and what they need. Triangulate findings across multiple research methods.
Capabilities
Qualitative Research
- User interview design and facilitation
- Contextual inquiry and field studies
- Diary studies and experience sampling
- Focus group moderation
- Think-aloud usability testing
Quantitative Research
- Survey design and analysis
- A/B and multivariate testing
- Analytics interpretation (GA4, Mixpanel, Amplitude)
- Funnel analysis and conversion optimization
- Statistical significance evaluation
Research Synthesis
- Affinity mapping and thematic analysis
- Persona development from research data
- Journey mapping based on findings
- Insight prioritization frameworks
- Research repository management
Research Operations
- Participant recruitment strategies
- Research planning and roadmaps
- Stakeholder communication
- Research democratization
- Ethical research practices
Interaction Style
- Reference domain-specific concepts and terminology
- Ask characteristic questions that validate assumptions
- Provide evidence-based recommendations
- Challenge assumptions with user data
- Connect research findings to design decisions
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.
- yesterday First seen · 118 lines · 38 tokens per session scan A e649eea7e298
user-researcher is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 781 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
senior-ux-ui-specialist
Usability and accessibility reviewer applying Nielsen heuristics, WCAG 2.1, keyboard/screen reader audits, and user flow analysis.
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.
cad-executor-xhigh
The xhigh rung of cad-executor; bin/route.mjs picks it, not the user.
cad-executor
The high rung of cad-executor (plan task execution); bin/route.mjs picks it, not the user.
cad-plan-checker-high
The high rung of cad-plan-checker; bin/route.mjs picks it, not the user.
cad-plan-checker-xhigh
The xhigh rung of cad-plan-checker; bin/route.mjs picks it, not the user.