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 prepforeverything/prepkit-product --skill product-opportunity-mappinggit clone --depth 1 https://github.com/prepforeverything/prepkit-productWrote 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/prepforeverything/prepkit-product/product-opportunity-mapping)<a href="https://agentmods.dev/skills/prepforeverything/prepkit-product/product-opportunity-mapping"><img src="https://agentmods.dev/badge/skills/prepforeverything/prepkit-product/product-opportunity-mapping/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/skills/prepforeverything/prepkit-product/product-opportunity-mapping"><img src="https://agentmods.dev/badge/skills/prepforeverything/prepkit-product/product-opportunity-mapping.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.00040 | $0.01234 |
| Opus 5 | $0.00020 | $0.00617 |
| Sonnet 5 | $0.00008 | $0.00247 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
product-opportunity-mapping 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 9d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standalone Mode: This skill is part of the prepkit-product plugin.
spec/product-context.mdis optional — provide context inline or create one from the template.- Output paths (
research/,reports/) are relative to your current working directory.- Facilitation routing is advisory — invoke any skill directly.
Product Opportunity Mapping
When To Use
- Discovery has evidence but the team has not chosen which opportunity to pursue
- Multiple unmet needs or frictions compete for attention
- The team is slipping from user opportunities into feature lists
- A defer or monitor decision needs explicit revisit triggers
Key Concepts
- Outside-in opportunity framing: start from customer friction, not planned features
- Pursue / monitor / defer: three decision states with different commitment levels
- Capability fit: what the team can realistically support right now
- Revisit triggers: the evidence or dependency change that should reopen a decision
Rules
- Opportunity statements must stay in customer language
- "Do nothing" or "not now" is a valid outcome
- When several opportunities are viable, recommend the one with the highest expected user-outcome gain per current delivery effort and defer the rest with explicit revisit triggers — chasing many opportunities simultaneously dilutes impact and extends delivery.
- This workflow owns
research/opportunity-map.mdandreports/opportunity-decision.md - Discovery may invoke this skill, but does not own its artifact paths
- Rank opportunities by expected user-outcome change, not by solution complexity or feature count — an opportunity that changes one critical user behavior outweighs three that ship features without measurable impact
- Apply all output quality gates from
references/product-quality-gates.md. - Every
deferdecision must include an explicit revisit trigger in the format: "Revisit when [specific condition or evidence change]." A defer without a trigger is a silent discard — the item will never return to consideration. - Before finalizing pursue decisions, check for cannibalization: would pursuing this opportunity reduce the value of an existing product or another pursued opportunity? If yes, quantify the overlap and factor it into the decision.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 90 lines · 40 tokens per session scan A 03e86e1bdd56
product-opportunity-mapping is a skill published in the GitHub repository prepforeverything/prepkit-product (2 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,234 once invoked, about $0.0002 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-31.
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…
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…
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…