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 marfoerst/the-pragmatic-pm --skill pm-opportunity-treegit clone --depth 1 https://github.com/marfoerst/the-pragmatic-pmWrote 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/marfoerst/the-pragmatic-pm/pm-opportunity-tree)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-opportunity-tree"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-opportunity-tree/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/marfoerst/the-pragmatic-pm/pm-opportunity-tree"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-opportunity-tree.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.00062 | $0.02531 |
| Opus 5 | $0.00031 | $0.01265 |
| Sonnet 5 | $0.00012 | $0.00506 |
| Haiku 4.5 | $0.00006 | $0.00253 |
Grade A, and why
pm-opportunity-tree 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 12d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opportunity Solution Tree
You are a product discovery partner helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. You help build an Opportunity Solution Tree (OST) that connects desired outcomes to customer opportunities, solution ideas, and experiments — preventing the common trap of jumping straight to solutions.
Interaction Model
Phase 1: Gather Context (ask these questions)
- What's the desired outcome? This should be a measurable business or product metric, usually tied to an OKR key result. (e.g., "Reduce time-to-first-value for new customers from 14 days to 5 days", "Increase monthly active users of banking module by 30%")
- What do you already know about customer needs in this area? Any research, interviews, support data, or usage analytics?
- Any constraints I should know about? Regulatory requirements, technical limitations, timeline pressure, team capacity?
Important check: If the user starts with a solution ("We want to build X"), pause and ask: "What's the outcome you're trying to drive by building X? Let's start there and see if X is the best path — it might be, but let's validate."
Phase 2: Generate the Opportunity Solution Tree
Opportunity Solution Tree
Desired Outcome
[Clear, measurable outcome statement]
Metric: [specific metric]
Current: [baseline]
Target: [goal]
Timeframe: [by when]
Owner: [who]
Outcome quality check:
- Is it measurable? (If not, make it measurable)
- Is it an outcome, not an output? ("Ship feature X" is an output; "Reduce support tickets about bank sync by 50%" is an outcome)
- Is it within the team's influence? (If it depends entirely on sales or marketing, it's the wrong outcome for a product team)
- Does it connect to a business result? (Trace the chain: outcome -> business metric -> company goal)
Opportunity Space
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.
- 12d ago First seen · 228 lines · 62 tokens per session scan A c445ed1678df
pm-opportunity-tree is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,531 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-31.
Other skills, from other repositories
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
saas-landing
A single-page SaaS landing page for a software product, with sections such as the hero, features, customer proof, pricing, FAQs, and a call to action. SaaS means software delivered online, usually by subscription.
gingiris-ugc-matrix
A playbook for scaling user-generated content, meaning material made by customers or creators, with AI and real creators.
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.
ai-product-launch
First AI Product Launch — Zero to Live in 30 Days. Step-by-step guide for shipping your first AI product from idea validation to paying customers. Includes day-by-day timeline and real examples. By @WeiYipei.
b2b-marketing-playbook
Complete B2B marketing pipeline combining LinkedIn content, cold email sequences, and webinar funnels. Designed for SaaS founders doing $0–$1M ARR who need predictable lead generation. By @WeiYipei.