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 ljucask/pureinn-product-development --skill pm-problem-validationgit clone --depth 1 https://github.com/ljucask/pureinn-product-developmentWrote 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/ljucask/pureinn-product-development/pm-problem-validation)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-problem-validation"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-problem-validation.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.1 | $0.00054 | $0.04268 |
| Opus 5 | $0.00027 | $0.02134 |
| Sonnet 5 | $0.00011 | $0.00854 |
| Haiku 4.5 | $0.00005 | $0.00427 |
Grade A, and why
pm-problem-validation 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 8d 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Problem Validation Summary
Agent mode (--agent)
Supports --agent: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note.
- No flag → interactive (default); if inputs are heavy, offer agent mode.
--agent→ obey. First check inputs are complete. Anything missing: do NOT invent it - mark[ASSUMED - what/why]in the output and summary. Never hallucinate to fill a gap.- Review required: the artifact contains commitments - after drafting, require the user's review before finalizing; do not close decisions autonomously.
What this skill does
Synthesizes all Phase 2 Track outputs into one convergence document:
- Track A: Tech Feasibility Report
- Track B: Domain Analysis + Legal Requirements
- Track C: Market Analysis (TAM/SAM/SOM, Competitor Analysis, SWOT, Market Timing)
- Track D: Personas + JTBD Analysis
This is the Phase 2 exit artifact. Its output becomes the primary input to Phase 3a (Design Thinking - Define stage).
No new research. Claude reads all inputs and synthesizes patterns, validates consistency, and surfaces contradictions.
Dependencies
Strongly recommended before running (this skill synthesizes all of them):
pm-tech-feasibility- Track Apm-domain-analysis- Track Bpm-market-analysis- Track Cpm-personas- Track D (Step 1)jtbd-building- Track D (Step 2)
Produces artifacts used by:
pm-prd- Problem Validation Summary is a primary PRD inputdesign-thinking- feeds the Define stage (problem statement, POV)pm-product-roadmap- problem and market context for roadmap framing
Step 0: Current state check
Check for existing artifacts:
- Problem Validation Summary
Then check which Track inputs are available:
| Track | Artifact | Status |
|---|---|---|
| A - Tech | Tech Feasibility Report | ✅ / ⚠️ / ❌ |
| B - Domain | Domain Analysis + Legal Requirements | ✅ / ⚠️ / ❌ |
| C - Market | Market Analysis (all 4 artifacts) | ✅ / ⚠️ / ❌ |
| D - VOC | Personas + JTBD Analysis | ✅ / ⚠️ / ❌ |
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.
- 8d ago First seen · 426 lines · 54 tokens per session scan A 06496f2d8693
pm-problem-validation is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 28d ago), licensed MIT. It adds 54 tokens to every session and 4,268 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
ai-native-design
A workflow for turning a product brief and API contract into frontend design prompts and implementation guidance. It supports three outside design channels and keeps generated frontend work aligned with the same brief and contract.
backend-development
A set of instructions for building server-side code such as APIs and database-backed applications. It uses API contracts, data models, the chosen technology stack, and tests as the project’s reference points.
decision-gate
A decision checkpoint for software-project workflows. After each phase produces its files, it asks the user to accept the result, request a change, add information, or regenerate it before the next phase begins.
frontend-development
A set of instructions for building the user-facing part of a web application, such as its pages, controls, and interactions. It applies to single-page applications and follows the project’s API, product, technology, and design documents.
relay
A Chinese-language procedure for handing an unfinished task from one AI session to another without losing its context.
validation-loop
A development routine that checks each important file immediately after it is changed by running the project’s build, lint, type-check, or test commands.