What is research-users?

A command for turning user research into personas, behavioral groups, and customer journey maps. It can work from surveys, interviews, support tickets, analytics, satisfaction data, or a product description.

Use it to understand who your users are, how groups differ, where they encounter friction, and what changes the research supports.

It organizes scattered research into a form that supports decisions about users, product direction, positioning, pricing, and onboarding.

research-users — Command for Claude Code by unixcrh/phuryn-pm-skills

Install

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.

Clone the repo

git clone --depth 1 https://github.com/unixcrh/phuryn-pm-skills

Made for: Claude Code.

Or install pm-market-research, the plugin that ships this one along with the rest of its 7 skills, 3 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/research-users/github.svg)](https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/research-users)

Your own site

<a href="https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/research-users"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/research-users/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/research-users"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/research-users.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 936 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00019	$0.00936
Opus 5.5	$0.00008	$0.00374
Sonnet 5.5	$0.00004	$0.00187
Haiku 4.5	$0.00002	$0.00094

Measured 2mo ago against content hash 2de91d824085, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-users 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 2mo 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.

Origin

This is a copy

100% identical to research-users — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

pm-market-research/commands/research-users.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/research-users -- User Research Synthesis

Turn raw research data into actionable user personas, behavioral segments, and customer journey maps. Accepts survey data, interview notes, feedback, analytics, or a product description for exploratory research.

Invocation

/research-users [upload survey results, interview notes, or feedback data]
/research-users B2B project management tool for agencies — help me understand our users
/research-users [paste user feedback or support ticket data]

Workflow

Step 1: Accept Research Inputs

Accept from any combination:

Survey responses (CSV, spreadsheet, pasted)
Interview notes or transcripts
Support tickets or feature requests
Product analytics / behavioral data
NPS or satisfaction data
Product description (for exploratory research without data)

Ask:

What research do you have? What format?
What do you want to understand? (who are our users, how do they differ, where's the friction)
What decisions will this inform? (roadmap, positioning, pricing, onboarding)

Step 2: Build Personas

Apply the user-personas skill:

Identify 3-4 distinct personas from the data
For each persona: name, role, goals (JTBD), pains, gains, behavioral patterns
Include unexpected insights — things that surprised you in the data
Note persona prevalence (what % of your base each represents, if data allows)

Step 3: Segment Users

Apply the user-segmentation and market-segments skills:

Create behavioral segments (not just demographics)
For each segment: size, JTBD, product fit, willingness to pay, engagement level
Identify the highest-value segment and the highest-growth segment
Map segments to personas (how they overlap)

Step 4: Map the Customer Journey

Apply the customer-journey-map skill:

Map the end-to-end journey: Awareness → Consideration → Onboarding → Active Use → Expansion → Advocacy
For each stage: touchpoints, emotions, pain points, aha moments
Identify the biggest drop-off points
Highlight moments of delight worth amplifying

Read the full file on GitHub · 122 lines

Changes

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.

2mo ago First seen · 122 lines · 19 tokens per session scan A 2de91d824085

Subscribe to this mod's changes

research-users is a command published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 8mo ago), licensed MIT. It adds 19 tokens to every session and 936 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to research-users, differing in 0 lines, and is treated as a copy.

Research

research-users next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
research-usersunixcrh/phuryn-pm-skills	Command	2	8mo ago	MIT	A	19	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	today	MIT	A	14	Claude Code