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 design-thinkinggit 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/design-thinking)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/design-thinking"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/design-thinking/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/ljucask/pureinn-product-development/design-thinking"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/design-thinking.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.00068 | $0.03910 |
| Opus 5 | $0.00034 | $0.01955 |
| Sonnet 5 | $0.00014 | $0.00782 |
| Haiku 4.5 | $0.00007 | $0.00391 |
Grade A, and why
design-thinking 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 9d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Design Thinking (Define + Ideate)
Agent mode (--agent)
This skill's value is the live dialogue - --agent is not supported. If invoked with --agent, warn once ("this skill needs interactive back-and-forth; agent mode would hollow it out") and proceed interactively.
What this skill does
Applies the Define and Ideate stages of Design Thinking to Phase 2 research outputs. In the context of this framework, Empathize is already done (Phase 2 discovery). This skill picks up at Define.
Produces:
- Problem Statement - precise articulation of the validated problem
- Point of View (POV) - user + need + insight framing
- How Might We (HMW) questions - opportunity reframing
- Ideation synthesis - promising solution directions from structured brainstorming
This skill runs once in Phase 3a. It is the bridge between discovery (what we learned about the problem) and validation strategy (what we will test before committing to building).
Output informs the Business Model Canvas, PRD framing, and product vision.
Dependencies
Required before running:
pm-problem-validation- the Problem Validation Summary is the primary inputpm-personas- persona and JTBD context frames the POV
Recommended before running:
jtbd-building- Forces Diagram provides the HMW framing materialpm-market-analysis- competitive whitespace informs ideation
Produces artifacts used by:
pm-business-model- solution direction from ideation informs value proposition choicespm-prd- Problem Statement and POV are core PRD sectionspm-product-roadmap- product vision emerges from ideation synthesis
Step 0: Current state check
Check for existing artifacts:
- Design Thinking synthesis (Define + Ideate output)
- Problem Statement
- POV Statement
- HMW Questions
- Ideation synthesis
Also check: does a Problem Validation Summary exist? Does a JTBD Analysis exist? These are required inputs. Without them, the Define stage will be built on unvalidated assumptions.
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.
- 9d ago First seen · 410 lines · 68 tokens per session scan A 4e3ff1e3d2db
design-thinking is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 3,910 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.