pm-brain: Command for Claude Code

.claude/skills/pm-brain/scaffold/.claude/commands/hypothesize.md

hypothesize is a command for Claude Code from phuryn/pm-brain. It costs 0 tokens per session (789 once invoked), scanned A, original, MIT.

A command that creates or refreshes hypotheses about a product feature or problem. A hypothesis is a testable explanation or assumption about what may happen or why something happens.

In plain words
What is it for?
Use it before launch to identify risks, or after launch to investigate analytics, interviews, churn, or declining retention.
Why use it?
It keeps assumptions tied to strategy, user evidence, recent observations, and the stage of the feature.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is phuryn/pm-brain's own configuration. It tells Claude Code how to work on pm-brain 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-brain configures →

Reuse

Borrowing it

Nothing to install: this file belongs to phuryn/pm-brain. 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/phuryn/pm-brain/main/.claude/skills/pm-brain/scaffold/.claude/commands/hypothesize.md
Clone the repo
git clone --depth 1 https://github.com/phuryn/pm-brain

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 hypothesize

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/phuryn/pm-brain/hypothesize"><img src="https://agentmods.dev/badge/commands/phuryn/pm-brain/hypothesize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 789 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.00000 $0.00789
Opus 5.5 $0.00000 $0.00316
Sonnet 5.5 $0.00000 $0.00158
Haiku 4.5 $0.00000 $0.00079

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

Security

Grade A, and why

hypothesize 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 1mo 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/skills/pm-brain/scaffold/.claude/commands/hypothesize.md · 42 lines

How it starts

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

/hypothesize

Generate or refresh hypotheses for a feature. Works pre-ship (proactive, organized by the 5 risk areas) or post-ship (data-derived from analytics / interviews / churn — "why is retention dropping?"). Same schema either way; the Origin field distinguishes them.

Input

A feature slug (/hypothesize weekly-digest), a problem statement (/hypothesize "mid-market onboarding drop-off"), or an existing hypothesis file to refresh (/hypothesize hypotheses/weekly-digest.md).

If the feature has no existing file yet, the command creates one. If it does, the command refreshes — opening new candidate hypotheses where evidence has accumulated, and surfacing any existing ones whose evidence has gone stale.

Loads

  • hypotheses/<slug>.md if it exists (refresh mode)
  • knowledge/product/features/<slug>.md (if the feature exists in product knowledge)
  • knowledge/strategy.md — non-goals, priorities, north-star (so the hypotheses don't violate strategic constraints)
  • knowledge/users/insights.md and any relevant personas.md / segments.md
  • Recent ingestion/ filtered to this feature / problem space (interviews, meeting notes, market signals — last ~10 entries)
  • decisions/ filtered to ones that constrain or invalidate hypothesis space for this feature
  • hypotheses/_SCHEMA.md — load before writing or refreshing any hypothesis file

Updates

  • hypotheses/<slug>.md — created (new feature) or appended (refresh mode). Each new hypothesis carries: belief, origin (proactive | data-derived from <source>), confidence (always start at low for new hypotheses), evidence-for / evidence-against (tagged), open questions, test plan, decision trigger, status (active).
  • hypotheses/INDEX.md — add the file under the appropriate status section if newly created; update status if a hypothesis flipped state.
  • Maintenance log entry — one-line note that hypotheses were generated/refreshed for <feature> with a count of new and modified.

Hard constraints:

Read the full file on GitHub · 42 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.

  1. 1mo ago First seen · 42 lines · 0 tokens per session scan A 824688d9bbee

Subscribe to this mod's changes

hypothesize is a command published in the GitHub repository phuryn/pm-brain (941 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 789 tokens. 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.