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 aakashg/pm-claude-skills --skill idea-validatorgit clone --depth 1 https://github.com/aakashg/pm-claude-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/aakashg/pm-claude-skills/idea-validator)<a href="https://agentmods.dev/skills/aakashg/pm-claude-skills/idea-validator"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-skills/idea-validator/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/aakashg/pm-claude-skills/idea-validator"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-skills/idea-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.02147 |
| Opus 5 | $0.00030 | $0.01073 |
| Sonnet 5 | $0.00012 | $0.00429 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
idea-validator 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 11d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Validator
Stress-test a product idea across 5 dimensions and return a GO / ITERATE / STOP verdict with evidence.
Step 0 — Read first
| Source | Path | What to extract |
|---|---|---|
| Project context | CLAUDE.md |
Company, market, target users, current focus |
| Scoring rubric | references/scoring-rubric.md |
Strong/Moderate/Weak bar for each dimension |
| User's materials | any doc, deck, or notes they name | Actual customer quotes, usage data, pricing research |
| Existing research | docs/, research/ if present |
Prior validation on the same problem |
If the user names no materials, say so explicitly in the verdict. An idea validated only against your training data is a hypothesis, not a validation, and you must label it that way.
Constraints
Mandatory. These override the user's enthusiasm.
- Every rating requires 3–5 sentences of specific reasoning. A rating with no evidence is invalid.
- Never rate STRONG without a named comparable, a number, or a cited user behavior.
- Never default to GO because the user is excited. Honesty is the deliverable.
- Never treat "no competitors" as opportunity. It usually means no market. Say so.
- Never recommend "build the MVP" as the first next step.
- Flag every guess with
ASSUMPTION:and name the data that would confirm or deny it. - Flag every missing input with
[NEED: X]. - Never give all five STRONGs unless the evidence is genuinely exceptional. Most ideas are a mix.
- Name what is hard and why. "This could be challenging" is not a risk.
Existence check
Before scoring anything, verify three things:
- Problem — a specific pain, stated in the user's own words, with a frequency.
- User — a named segment: job title, company size, situation. "Everyone" and "businesses" fail this check.
- Evidence — one real signal: a customer quote, a support ticket volume, a competitor's pricing page, a workaround they observed.
If two of three are missing, refuse to score. Say which are missing and ask for exactly those. Scoring an idea with no user and no evidence produces a confident number built on nothing, which is worse than no analysis.
What ships with it
1 file 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.
- 11d ago First seen · 177 lines · 59 tokens per session scan A bb421b063bbb
idea-validator is a skill published in the GitHub repository aakashg/pm-claude-skills (106 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,147 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-30.
Other skills, from other repositories
utility-pm-skill-builder
Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.
utility-update-pm-skills
Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip options. Produces an update report listing changed files, skipped files, and new capabilities. Use when you want to bring a local pm-skills…
discover-journey-map
Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one phase. Without research signal yet…
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
utility-pm-skill-validate
Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.
tool-foundation-sprint-founding-hypothesis
Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe, what-could-prove-us-wrong, and recommended next validation step. Use after Magic Lenses is signed. Strict canonical…