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 agentmods add skills/adidacta/pmf-detective/validation-plan-buildernpx skills add adidacta/pmf-detective --skill validation-plan-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/validation-plan-builder)<a href="https://agentmods.dev/skills/adidacta/pmf-detective/validation-plan-builder"><img src="https://agentmods.dev/badge/skills/adidacta/pmf-detective/validation-plan-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 | $0.00056 | $0.02025 |
| Opus 5 | $0.00028 | $0.01012 |
| Sonnet 5 | $0.00011 | $0.00405 |
| Haiku 4.5 | $0.00006 | $0.00202 |
Grade A, and why
validation-plan-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 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Plan Builder
You help product builders decide HOW to test their PMF assumptions and create a concrete plan. The validation plan is a decision point — it determines what happens next (landing page, outreach, or build).
Context
The PMF context layer (ICP, Value Prop, MVP PRD) is based on assumptions. This skill helps users choose a validation method, define success criteria, and route to the right execution skill.
Prerequisites
Check if the context layer exists:
pmf/icp.md(required)pmf/value-prop.md(required)pmf/mvp.md(required — the MVP PRD)
If missing, inform user: "Let's build your PMF context first, then create a validation plan."
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.
- Ground options in ICP data (where to find them, how they talk, pain intensity)
- Include "Not sure (needs research)" option on every question — adds to Open Questions with context
The Flow
Phase A: Summarize Assumptions (automated — no questions)
Read all three context files and extract the core assumptions being tested:
- ICP assumption: [This person] experiences [this pain]
- Value prop assumption: [This message] will make them say "that's me" and take action
- MVP assumption: [This aha moment] is what they need to experience
Display:
┌───────────────────────────────────────────────────────────────┐
│ YOUR ASSUMPTIONS │
├───────────────────────────────────────────────────────────────┤
│ │
│ 1. [ICP identity] experiences "[pain]" │
│ 2. "[Value prop message]" will grab their attention │
│ 3. "[Aha moment]" is the experience that converts them │
│ │
│ Everything you've built so far is based on these. │
│ Now let's figure out how to test them. │
│ │
└───────────────────────────────────────────────────────────────┘
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.
- 5d ago First seen · 209 lines · 56 tokens per session scan A b6121125b331
validation-plan-builder is a skill published in the GitHub repository adidacta/pmf-detective (18 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 2,025 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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…