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-prototypegit 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-prototype)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-prototype"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-prototype/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/pm-prototype"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-prototype.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.00000 | $0.08837 |
| Opus 5.5 | $0.00000 | $0.03535 |
| Sonnet 5.5 | $0.00000 | $0.01767 |
| Haiku 4.5 | $0.00000 | $0.00884 |
Grade A, and why
pm-prototype 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 18d 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 — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Prototype (validate before real build)
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: a run contains commitments - whether to prototype at all, the audience, the path, the classification, and at Step 8 the verdict and the kill / promote decision. A subagent drafts each as a proposal; none is final until the user has reviewed it. Wrap mode makes none of these decisions and runs fully.
Standalone run
Runs with or without a Pureinn workspace - it needs no other skill's artifact, so it works as a single tool from an install that never ran /pureinn.
- No workspace: create just the folder this skill writes into, or write to a path the user names, and say where the file went. Do not scaffold a project, do not invent a
state.json, and do not send the user to/pureinnfirst. - Read
pureinn-variables.md/state.jsonwhere a value is actually used, not at the top of the run. Missing value: continue and name the capability it costs.
Artifact language
Checks state.json → artifact_language. Default (unset, "English", or no workspace): no change in behavior.
- If set to a non-English language: write prose content in that language -
meta.md,hypotheses.md,findings.md, the feature plan and cards, the spec's descriptive sections. - Never translate: IDs (
PRT-,FEAT-,OQ-), field labels a later run reads and their values (Decision:,Classification:,Path:, the four verdict states,built/next/cut), file names - these stay English always, regardless of the setting. - This is not the language the prototype itself speaks. That is asked separately at Step 3b (
references/content-and-copy.md), and the two can differ.
What ships with it
23 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.
- references/audience-depth.md 5.7 KB
- references/content-and-copy.md 6.6 KB
- references/design-direction.md 8.4 KB
- references/external-tools.md 10 KB
- references/hypotheses.md 13 KB
- references/in-repo-loop.md 39 KB
- references/promotion.md 5.6 KB
- references/prototype-folder.md 14 KB
- references/published-review.md 5.5 KB
- references/scaffold/check.py 5.0 KB runs code
- references/scaffold/harness-client.js 11 KB runs code
- references/scaffold/harness.config.js 29 KB runs code
- references/scaffold/harness.html 463 KB
- references/scaffold/HISTORY.md 26 KB
- references/scaffold/publish.py 9.3 KB runs code
- references/scaffold/pull.py 11 KB runs code
- references/scaffold/README.md 53 KB
- references/scaffold/serve.py 14 KB runs code
- references/scaffold/sync.py 14 KB runs code
- references/showing.md 6.2 KB
- references/spec-artifact.md 3.8 KB
- references/way-in.md 9.9 KB
- references/workbench.md 9.0 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.
- 18d ago Changed · +2 lines 4424c150be82
- 19d ago Changed · +37 lines · -215 tokens per session 6e5dd5fe835f
- 1mo ago Changed · +24 tokens per session ce4a9a0f9e5b
- 1mo ago Changed · +5 lines · +37 tokens per session 885516c482bc
- 1mo ago First seen · 426 lines · 154 tokens per session scan A 0f86e49ffa9c
pm-prototype is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 8,837 tokens. 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.
interface-craft
Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or…
presentation-design
Designs slide decks and one-pagers that carry an argument rather than decorate one — deck structure, headlines that state the takeaway, charts that make a single point, and the different rules board decks and conference talks follow. Use this to build or fix a pitch deck, board deck, or conference talk, to design a…
design-styles
Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions…
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…