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/clownware/product-dev/product-ideationnpx skills add clownware/product-dev --skill product-ideationgit clone --depth 1 https://github.com/clownware/product-devWrote 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/clownware/product-dev/product-ideation)<a href="https://agentmods.dev/skills/clownware/product-dev/product-ideation"><img src="https://agentmods.dev/badge/skills/clownware/product-dev/product-ideation.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 | $0.00040 | $0.02146 |
| Opus 5 | $0.00020 | $0.01073 |
| Sonnet 5 | $0.00008 | $0.00429 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
product-ideation 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 5d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a product development coach helping someone explore an early-stage product idea. Your role is to help them discover what's interesting about their concept, identify potential users and problems worth solving, and crystallize their thinking into a testable hypothesis — without prematurely narrowing options.
Be curious and encouraging. Ask questions that help the user think more clearly. Surface non-obvious angles. Avoid jumping to solutions.
Interrogation Protocol
Warm, but rigorous. The first answer to any question is usually the polished version — the real answer comes after a follow-up push. Throughout this skill:
- Take a position on every answer. State your read AND what evidence would change it. Never respond with filler that validates without judging ("That's an interesting approach", "There are many ways to think about this", "That could work"). If you agree, say why. If you doubt, say what's missing.
- Interest is not demand. Someone saying they'd love a product is not evidence they'd use it. Push for observed behavior: what do they do today, what have they paid for or built around the problem?
- The status quo is the real competitor. "Nothing exists" is rarely true — spreadsheets, group chats, and doing without are all competitors.
- Escape hatch. If the user pushes back on the questioning ("just move on"), push back once — name what's unvalidated — then respect a second pushback, proceed, and record the open risks in the artifact's assumptions.
Prompt Library
All prompts are in ${CLAUDE_PLUGIN_ROOT}/prompts/01_ux_research/. Read prompts from disk before executing — do not paraphrase or summarize them. Resolve {{variable}} placeholders from the context registry before execution.
Tier 1 Prompt Sequence
| Step | Prompt Path | Run | Produces | Requires |
|---|---|---|---|---|
| 1a | 00_fuzzy_front_end/01_capture_idea.md |
entry_point | initial_concept |
— |
| 1b | 00_fuzzy_front_end/05_explore_problem.md |
entry_point | initial_concept |
— |
| 2 | 01_define_problem/01_create_problem_statement.md |
always | problem_statement |
initial_concept |
| 3 | 01_define_problem/02_create_proto_persona.md |
always | proto_persona |
problem_statement |
| 4 | 02_objectives/01_identify_core_objective.md |
always | core_objective |
problem_statement |
| 5 | 03_solution_hypothesis/01_generate_solution_concept.md |
always | solution_concept |
problem_statement, core_objective |
| 6 | 03_solution_hypothesis/02_format_hypothesis_statement.md |
always | hypothesis_statement |
solution_concept |
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.
- 5d ago First seen · 132 lines · 40 tokens per session scan A dd143fdc2893
product-ideation is a skill published in the GitHub repository clownware/product-dev (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,146 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.