plan-pmf

plan-pmf is a command for coding agents from adidacta/pmf-detective. It costs 8 tokens per session (414 once invoked), scanned A, original, MIT.

A guided planning command for defining product–market fit (PMF)—the match between a product and a real customer need. It helps document your target customer, value proposition, MVP, and validation plan.

In plain words
What is it for?
Use it to define your ideal customer profile, explain why customers should care, set the MVP’s scope and requirements, and plan how to test your assumptions.
Why use it?
It turns broad product ideas into a written plan and shows whether planning documents already exist. This reduces the risk of restarting work or leaving key assumptions undefined.

Command

Part of the plan-pmf plugin — 9 skills, 6 commands shipped together

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.

agentmods
npx agentmods add commands/adidacta/pmf-detective/plan-pmf
Clone the repo
git clone --depth 1 https://github.com/adidacta/pmf-detective

Or install plan-pmf, the plugin that ships this one along with the rest of its 9 skills, 6 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.

agentmods badge for plan-pmf

README.md
[![agentmods](https://agentmods.dev/badge/commands/adidacta/pmf-detective/plan-pmf.svg)](https://agentmods.dev/commands/adidacta/pmf-detective/plan-pmf)
Your own site
<a href="https://agentmods.dev/commands/adidacta/pmf-detective/plan-pmf"><img src="https://agentmods.dev/badge/commands/adidacta/pmf-detective/plan-pmf.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 414 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.00414
Opus 5 $0.00004 $0.00207
Sonnet 5 $0.00002 $0.00083
Haiku 4.5 $0.00001 $0.00041

Measured 5d ago against content hash 031f25754de3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-pmf 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 5d 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.

commands/plan-pmf.md · 57 lines

What it actually says

PMF Plan

Start the guided flow to build your complete PMF context layer.

Instructions

This command triggers the plan-pmf-mode skill which guides users through:

  1. ICP (Who your customer is)
  2. Value Proposition (Why they should care)
  3. MVP (Scope, features & requirements)
  4. Validation Plan (How you'll test your assumptions)

Read the plan-pmf-mode SKILL.md and follow its process.

Check for Existing Context

First, use Glob to check what already exists in pmf/:

  • pmf/icp.md
  • pmf/value-prop.md
  • pmf/mvp.md

If any exist, show what's already defined and ask: "You already have some context defined. Would you like to:

  1. Start fresh (will overwrite existing files)
  2. Continue from where you left off
  3. Update a specific section"

Starting Fresh

Begin with the welcome message:

┌───────────────────────────────────────────────────────────────┐
│  PMF CONTEXT BUILDER                                          │
├───────────────────────────────────────────────────────────────┤
│                                                               │
│  Let's build your PMF context layer.                          │
│                                                               │
│  We'll work through 4 sections:                               │
│  1. ICP - Who your customer is                                │
│  2. Value Proposition - Why they should care                  │
│  3. MVP - Scope, features & requirements                      │
│  4. Validation Plan - How you'll test assumptions             │
│                                                               │
│  Each section becomes a reference file Claude uses            │
│  when building anything for your product.                     │
│                                                               │
└───────────────────────────────────────────────────────────────┘

Then proceed through the plan-pmf-mode skill's question flow.

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. 5d ago First seen · 57 lines · 8 tokens per session scan A 031f25754de3

Subscribe to this mod's changes

plan-pmf is a command published in the GitHub repository adidacta/pmf-detective (18 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 414 once invoked, about $0.0000 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.