pm-prompts: Command for Claude Code

.claude/commands/research-plan.md

research-plan is a command for Claude Code from MrJoeSack/pm-prompts. It costs 12 tokens per session (305 once invoked), scanned A, original, MIT.

A command that turns a user-research goal into a structured plan for interviews, surveys, or usability tests. Usability tests watch people try a product to find where they struggle.

In plain words
What is it for?
Use it to define research questions, choose suitable activities, check for bias, and plan research about onboarding, customer needs, or product priorities.
Why use it?
It keeps research tied to a specific decision and helps avoid leading questions, combined questions, and confusing what people say with what they do.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is MrJoeSack/pm-prompts's own configuration. It tells Claude Code how to work on pm-prompts itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pm-prompts configures →

Reuse

Borrowing it

Nothing to install: this file belongs to MrJoeSack/pm-prompts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/MrJoeSack/pm-prompts/main/.claude/commands/research-plan.md
Clone the repo
git clone --depth 1 https://github.com/MrJoeSack/pm-prompts

Made for: Claude Code.

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.

agentmods badge for research-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/research-plan/github.svg)](https://agentmods.dev/commands/mrjoesack/pm-prompts/research-plan)
Your own site
<a href="https://agentmods.dev/commands/mrjoesack/pm-prompts/research-plan"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/research-plan/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.

agentmods 80×15 button for research-plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/mrjoesack/pm-prompts/research-plan"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/research-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 305 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 original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00305
Opus 5 $0.00006 $0.00152
Sonnet 5 $0.00002 $0.00061
Haiku 4.5 $0.00001 $0.00030

Measured 9d ago against content hash 068db692fcbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

research-plan 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 9d 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.

.claude/commands/research-plan.md · 40 lines

What it actually says

Research Plan Generator

Create research that informs real decisions. Apply research discipline:

Pre-Research Questions

Answer in one sentence each:

  1. What specific decision does this research inform?
  2. What would change your mind?
  3. What are you afraid to discover?

Research Design

  • Simple questions: "Why do you use this?" not "What factors influence utilization?"
  • One question per question: Don't hide multiple asks
  • Behavior over intention: Watch what they do, not what they say
  • Bias check: If this confirms what you believe, what did you learn?

The Hard Test

Write your research question in ten words or less. If you can't, you don't know what you're asking.

Input Template

Describe your research goal like: "I want to understand [what] so I can decide [specific decision]"

Examples:

  • "I want to understand why users abandon onboarding so I can decide whether to simplify the flow or improve messaging"
  • "I want to understand enterprise needs so I can decide which admin features to build first"

Output

Provide the research plan with question analysis and bias checks.

Arguments: {{args}}

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.

  1. 9d ago First seen · 40 lines · 12 tokens per session scan A 068db692fcbf

Subscribe to this mod's changes

research-plan is a command published in the GitHub repository MrJoeSack/pm-prompts (6 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 305 once invoked, about $0.0001 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-31.