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 wdavidturner/product-skills --skill monetizing-innovationgit clone --depth 1 https://github.com/wdavidturner/product-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/wdavidturner/product-skills/monetizing-innovation)<a href="https://agentmods.dev/skills/wdavidturner/product-skills/monetizing-innovation"><img src="https://agentmods.dev/badge/skills/wdavidturner/product-skills/monetizing-innovation/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/wdavidturner/product-skills/monetizing-innovation"><img src="https://agentmods.dev/badge/skills/wdavidturner/product-skills/monetizing-innovation.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.00080 | $0.01094 |
| Opus 5 | $0.00040 | $0.00547 |
| Sonnet 5 | $0.00016 | $0.00219 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
monetizing-innovation 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monetizing Innovation
What It Is
Monetizing Innovation is a framework for designing products that customers need, value, AND are willing to pay for. The core insight: price is not a number you slap on at the end — it's a measure of value that should guide what you build from the start.
The key shift: Move from "build the product, then figure out pricing" to "understand willingness to pay, then design the product around it."
72% of innovations fail from a monetization perspective — not because the product is bad, but because companies never validated that customers would actually pay for it.
Credit: This framework is based on Monetizing Innovation by Madhavan Ramanujam and Georg Tacke of Simon-Kucher & Partners, the world's leading pricing strategy consulting firm.
When to Use It
Use Monetizing Innovation when you need to:
- Validate product ideas before investing engineering resources
- Prioritize your roadmap based on what drives willingness to pay
- Choose a pricing model (subscription, usage, hybrid, outcome-based)
- Design packaging tiers (good/better/best) that convert
- Increase revenue without building new features
- Avoid leaving money on the table or underpricing
- Prepare for price negotiations in B2B sales
- Navigate pricing in a downturn without destroying value
When Not to Use It
- Commoditized markets where you have no pricing power
- Regulated pricing environments (healthcare, utilities)
- Very early discovery — you need a product concept to test willingness to pay against
- Consumer products with pure network effects where monetization must wait (though even then, understand your future model)
Patterns
Detailed examples showing how to apply Monetizing Innovation correctly. Each pattern shows a common mistake and the correct approach.
Critical (get these wrong and you've wasted your time)
| Pattern | What It Teaches |
|---|---|
| pricing-after-building | Have willingness to pay conversations BEFORE building, not after |
| asking-what-to-charge | Never ask "what should I charge?" — use relative and indirect methods |
| wrong-value-metric | The metric you charge on determines everything — get it right |
| giving-farm-away | 20% of features drive 80% of willingness to pay — don't give them away free |
| one-size-fits-none | Segment by needs and willingness to pay, not demographics |
What ships with it
16 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.
- patterns/_template.md 460 B
- patterns/asking-what-to-charge.md 1.8 KB
- patterns/cost-plus-pricing.md 1.9 KB
- patterns/discounting-to-close.md 2.2 KB
- patterns/features-not-benefits.md 1.7 KB
- patterns/giving-farm-away.md 2.0 KB
- patterns/ignoring-thresholds.md 1.8 KB
- patterns/land-without-expand.md 2.0 KB
- patterns/missing-decoy.md 1.9 KB
- patterns/one-size-fits-none.md 2.3 KB
- patterns/poc-without-commitment.md 2.2 KB
- patterns/pricing-after-building.md 1.7 KB
- patterns/rushing-pricing-model.md 1.9 KB
- patterns/static-segmentation.md 1.8 KB
- patterns/wrong-value-metric.md 1.6 KB
- references/monetizing-innovation-playbook.md 11 KB
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 · 89 lines · 80 tokens per session scan A 5de94a82f12b
monetizing-innovation is a skill published in the GitHub repository wdavidturner/product-skills (20 stars, last pushed 7mo ago), licensed MIT. It adds 80 tokens to every session and 1,094 once invoked, about $0.0004 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…
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…