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 Stijnman/grok-custom-skills --skill product-opportunity-treegit clone --depth 1 https://github.com/Stijnman/grok-custom-skillsWrote 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/stijnman/grok-custom-skills/product-opportunity-tree)<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/product-opportunity-tree"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/product-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/stijnman/grok-custom-skills/product-opportunity-tree"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/product-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.00042 | $0.00457 |
| Opus 5 | $0.00021 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
product-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.
What it actually says
Product Opportunity Tree
Purpose
Create an evidence-aware opportunity tree that connects a desired outcome to customer needs, candidate solutions, and assumption tests. Use it to avoid treating a feature idea as the problem definition.
Workflow
- Define one measurable outcome that the team can influence, including its current baseline if known.
- List customer opportunities as needs, barriers, or desired outcomes rather than proposed features.
- Attach evidence to each opportunity and label it as observed, reported, inferred, or unknown.
- Generate multiple solution options for promising opportunities; do not select a solution merely because it was proposed first.
- Identify the riskiest assumption for each selected solution and define the smallest ethical test that could reduce uncertainty.
- Prioritize the next branch using impact, confidence, effort, and evidence quality.
- Deliver a tree, evidence notes, open questions, and the next experiment.
Output format
Use a concise hierarchy: Outcome → Opportunities → Solutions → Assumption tests. Include a Mermaid diagram when it improves readability, but keep the textual hierarchy authoritative.
Quality boundaries
Do not invent research evidence, customer quotes, baselines, or business impact. Distinguish a hypothesis from a validated opportunity. Do not present the tree as a commitment or roadmap without the relevant stakeholder approval.
Error handling
| Situation | Response |
|---|---|
| Outcome is not measurable | Propose a measurable proxy and label it as a draft. |
| Evidence is sparse | Keep opportunities provisional and recommend discovery work before prioritization. |
| Solution list is already fixed | Record the constraint and identify the assumptions that still need testing. |
| Stakeholders disagree | Represent competing outcomes or assumptions rather than forcing a false consensus. |
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 · 44 lines · 42 tokens per session scan A 7f46b262591b
product-opportunity-tree is a skill published in the GitHub repository Stijnman/grok-custom-skills (9 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 457 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
goal-meta-skill
A guide for turning an unclear or complex task into a reviewable /goal instruction for coding agents.
workflow-to-skill
Turn a goal and existing CLI, MCP, HTTP, API, or external workflow capabilities into one reviewable reusable Agent Skill. Use when the user asks to create or revise a workflow SKILL.md without a dedicated interface for invocation or result presentation. A webpage, UI, image, or report produced as workflow output does…
rss-digest
Collect RSS or Atom sources and produce a traceable intelligence digest through the configured Weft workflow.
workflow-docs-sync
A project-documentation synchronisation workflow for rebuilding project facts from a local Git folder, GitHub repository, or current working directory, then updating core workflow documents.
workflow-to-skill-with-surface
Create or revise one reusable workflow Skill plus an optional harness-native Prompt Surface that maps a dedicated form, Page, button set, command UI, or result view to ordinary Skill messages and Harness results. Use only when the user explicitly requests a dedicated interface for invoking the Skill or presenting its…
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.