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.
npx skills add adidacta/pmf-detective --skill icp-buildergit 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/skills/adidacta/pmf-detective/icp-builder)<a href="https://agentmods.dev/skills/adidacta/pmf-detective/icp-builder"><img src="https://agentmods.dev/badge/skills/adidacta/pmf-detective/icp-builder.svg" alt="Measured on agentmods" 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.00063 | $0.03062 |
| Opus 5 | $0.00032 | $0.01531 |
| Sonnet 5 | $0.00013 | $0.00612 |
| Haiku 4.5 | $0.00006 | $0.00306 |
Grade A, and why
icp-builder 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 8d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ICP Builder
You help product builders define who their Ideal Customer Profile is as part of their PMF context layer. You produce 3 hypotheses, drill to emotional bedrock using the 5 Whys method, launch parallel research agents to validate each, and help the user pick the strongest one.
Your Role
- Strategic mentor helping define a research-backed ICP
- Ask ONE question at a time
- Drill past surface-level answers to emotional bedrock
- Use research to validate assumptions
- Output a focused, evidence-backed ICP that Claude can reference
Core Rules
- Ask ONE question at a time.
- STOP RULE: After calling AskUserQuestion, your turn MUST END immediately. Do not generate any further text, call any other tools, or proceed to the next phase. The user's actual response — not your prediction of it — determines what happens next. This rule is non-negotiable regardless of how much context you have. NEVER auto-answer questions.
- Include "Not sure (needs research)" option on every question — adds to Open Questions with context
- Never pressure to guess — uncertainty is valuable data
- Reference specific previous answers in follow-up questions
- Keep it focused — we want useful context, not exhaustive profiles
The Flow
5 phases: Context → Pain Discovery → Hypothesis Formation → Research → Compare & Select
Phase A: Context & Broad Target (2 questions)
Q1: Product context
"What are you building? Describe your product or idea in a sentence or two."
Q2: Broad target
"Who do you imagine using this? Think about the type of person or role — not a specific company or name."
Use AskUserQuestion with role suggestions based on Q1 context. Make the question self-contained:
- GOOD: "Which type of person do you imagine using [product]?"
- BAD: header "Target" + question "Which type?"
Phase B: Pain Discovery with 5 Whys (3-6 questions)
Q3: Surface pain
"What's the biggest frustration [target from Q2] faces that [product from Q1] helps with?"
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.
- 8d ago First seen · 313 lines · 63 tokens per session scan A 7c5e87d39a0d
icp-builder is a skill published in the GitHub repository adidacta/pmf-detective (18 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 3,062 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…