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.
git clone --depth 1 https://github.com/adidacta/pmf-detectiveWrote 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/commands/adidacta/pmf-detective/pmf-status)<a href="https://agentmods.dev/commands/adidacta/pmf-detective/pmf-status"><img src="https://agentmods.dev/badge/commands/adidacta/pmf-detective/pmf-status/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.
<a href="https://agentmods.dev/commands/adidacta/pmf-detective/pmf-status"><img src="https://agentmods.dev/badge/commands/adidacta/pmf-detective/pmf-status.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00006 | $0.01022 |
| Opus 5.5 | $0.00002 | $0.00409 |
| Sonnet 5.5 | $0.00001 | $0.00204 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
pmf-status 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PMF Status
Check the status of the user's PMF context layer.
Instructions
-
Use Glob to check for files in the
pmf/directory:pmf/icp.md→ ICP defined (assumption)pmf/value-prop.md→ Value proposition defined (assumption)pmf/mvp.md→ MVP scope defined (assumption)pmf/validation-plan.md→ Validation plan set
-
If files exist, read them to show summaries.
-
Display status:
If no pmf/ folder exists:
┌───────────────────────────────────────────────────────────────┐
│ PMF CONTEXT STATUS │
├───────────────────────────────────────────────────────────────┤
│ │
│ No PMF context layer found. │
│ │
│ The PMF context layer captures the "WHY" behind your │
│ product. Claude references these files when building │
│ anything for your product. │
│ │
│ The context layer: │
│ • icp.md - Who your customer is (assumption) │
│ • value-prop.md - Why they should care (assumption) │
│ • mvp.md - MVP scope & features (assumption) │
│ • validation-plan.md - How you'll test these assumptions │
│ │
├───────────────────────────────────────────────────────────────┤
│ Start: /plan-pmf to build your context layer │
└───────────────────────────────────────────────────────────────┘
Created by Adi Shmorak, The P/MF Detective
If partial context exists:
┌───────────────────────────────────────────────────────────────┐
│ PMF CONTEXT STATUS │
├───────────────────────────────────────────────────────────────┤
│ │
│ [✓] ICP (assumption) │
│ Who: [Brief summary from icp.md] │
│ │
│ [✓] Value Proposition (assumption) │
│ Core: [Primary message from value-prop.md] │
│ │
│ [ ] MVP (assumption) │
│ Not yet defined │
│ │
│ [ ] Validation Plan │
│ Not yet defined │
│ │
├───────────────────────────────────────────────────────────────┤
│ Progress: ██████████░░░░░░░░░░ 2/4 sections │
├───────────────────────────────────────────────────────────────┤
│ Next: /update-mvp to define your MVP scope │
└───────────────────────────────────────────────────────────────┘
Created by Adi Shmorak, The P/MF Detective
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 · 113 lines · 6 tokens per session scan A ac81197bdf86
pmf-status is a command published in the GitHub repository adidacta/pmf-detective (18 stars, last pushed 28d ago), licensed MIT. It adds 6 tokens to every session and 1,022 once invoked, about $0.0000 per session on Opus 5.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.
pmf-status compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pmf-statusadidacta/pmf-detective | Command | 18 | 28d ago | MIT | A | 6 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |