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/update-icp)<a href="https://agentmods.dev/commands/adidacta/pmf-detective/update-icp"><img src="https://agentmods.dev/badge/commands/adidacta/pmf-detective/update-icp/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/update-icp"><img src="https://agentmods.dev/badge/commands/adidacta/pmf-detective/update-icp.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.00004 | $0.00786 |
| Opus 5.5 | $0.00002 | $0.00314 |
| Sonnet 5.5 | $0.00001 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
update-icp 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update ICP
Update the ICP (Ideal Customer Profile) section of your PMF context layer.
Instructions
-
Check if
pmf/icp.mdexists- If exists: Read it and show summary, then present update menu
- If not: Inform user and offer to create it (trigger icp-builder skill)
-
If file exists, show current state:
┌───────────────────────────────────────────────────────────────┐
│ CURRENT ICP │
├───────────────────────────────────────────────────────────────┤
│ │
│ Selected: [Hypothesis name] │
│ Who: [Filtered persona summary] │
│ Pain: "[Emotional bedrock]" │
│ Evidence: Pain [X]/5 │ Access [X]/5 │ Evidence [X]/5 │
│ │
│ Alternatives on file: │
│ • [Hypothesis B name] │
│ • [Hypothesis C name] │
│ │
└───────────────────────────────────────────────────────────────┘
- Use AskUserQuestion with this menu:
"What would you like to update about your ICP?"
Options:
- Who They Are — Refine persona filters (company stage, tools, behaviors)
- Their Pain — Re-run 5 Whys deep dive to find emotional bedrock
- What They Want — Update goals and desired outcomes
- How They Talk About It — Update language and phrases
- Where To Find Them — Update channels and communities
- Switch to an alternative ICP — Promote one of the alternative hypotheses
- Re-run research validation — Launch fresh research agents for updated scores
- Start over completely — Re-run the full ICP builder from scratch
Option Details
Options 1, 3, 4, 5: Section updates
- Ask targeted follow-up questions for the selected section
- Update only that section in
pmf/icp.md - Preserve all other sections unchanged
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 · 92 lines · 4 tokens per session scan A 6f92a4c48d7b
update-icp is a command published in the GitHub repository adidacta/pmf-detective (18 stars, last pushed 28d ago), licensed MIT. It adds 4 tokens to every session and 786 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.
update-icp compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| update-icpadidacta/pmf-detective | Command | 18 | 28d ago | MIT | A | 4 | 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 |