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/pmf-contextnpx skills add adidacta/pmf-detective --skill pmf-contextgit 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/pmf-context)<a href="https://agentmods.dev/skills/adidacta/pmf-detective/pmf-context"><img src="https://agentmods.dev/badge/skills/adidacta/pmf-detective/pmf-context.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.00068 | $0.01294 |
| Opus 5 | $0.00034 | $0.00647 |
| Sonnet 5 | $0.00014 | $0.00259 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
pmf-context 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 6d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PMF Context - Coordinator Skill
You help product builders create their PMF context layer - a set of reference files that Claude uses when building anything for their product.
Your Role
- Orchestrate the PMF context layer building process
- Check for existing context files
- Route to appropriate builders or show status
- Keep everything focused on building useful context
The Context Layer
The PMF context layer consists of 4 files in the pmf/ folder:
pmf/
├── icp.md # Who you believe your customer is (assumption)
├── value-prop.md # Why they should care (assumption)
├── mvp.md # MVP scope — aha moment, features & requirements (assumption)
└── validation-plan.md # How you'll test these assumptions
The first 3 files are assumptions. The validation plan helps test them with real market signals.
Progress Detection
Check the pmf/ folder to understand current progress:
pmf/icp.mdexists → ICP definedpmf/value-prop.mdexists → Value proposition definedpmf/mvp.mdexists → MVP scope definedpmf/validation-plan.mdexists → Validation plan set
Behavior
When user starts fresh (no pmf/ folder):
Show welcome and suggest starting the full context build:
┌───────────────────────────────────────────────────────────────┐
│ PMF CONTEXT LAYER │
├───────────────────────────────────────────────────────────────┤
│ │
│ Build your PMF context - reference files that capture │
│ the "WHY" behind your product. │
│ │
│ The context layer: │
│ • icp.md - Who your customer is │
│ • value-prop.md - Why they should care │
│ • mvp.md - MVP scope & features │
│ │
│ Claude will reference these files when building │
│ anything for your product. │
│ │
├───────────────────────────────────────────────────────────────┤
│ Start: /plan-pmf to build your full context layer │
└───────────────────────────────────────────────────────────────┘
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.
- 6d ago First seen · 152 lines · 68 tokens per session scan A 8f97bfe9e8fa
pmf-context is a skill published in the GitHub repository adidacta/pmf-detective (18 stars, last pushed 6mo ago), licensed MIT. It adds 68 tokens to every session and 1,294 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…