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 AIDotNet/OpenCowork --skill product-design-prototypegit clone --depth 1 https://github.com/AIDotNet/OpenCoworkWrote 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/aidotnet/opencowork/product-design-prototype)<a href="https://agentmods.dev/skills/aidotnet/opencowork/product-design-prototype"><img src="https://agentmods.dev/badge/skills/aidotnet/opencowork/product-design-prototype.svg" alt="Measured on agentmods" 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.00047 | $0.01518 |
| Opus 5 | $0.00023 | $0.00759 |
| Sonnet 5 | $0.00009 | $0.00304 |
| Haiku 4.5 | $0.00005 | $0.00152 |
Grade A, and why
product-design-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 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Prototypes
You're tasked with creating a frontend-only, interactive website or app, that the user can click through and use.
Select the best workflow from the following options to solve the user's request
Golden Rule of Prototyping
- Do not build until you have a visual target and the chosen workflow reaches
$image-to-codeor$url-to-code. - A visual target is an app or website design to build from: a user-provided image, a source URL, or an ImageGen design selected by the user.
- A
$get-contextbrief is not a visual target. - After
$get-context, route to$ideateunless the user already provided a concrete visual source. - If
$ideatecreates options, stop and wait for the user to choose one. - The chosen option becomes the required visual target for
$image-to-code.
Critical Overrides
- Refer to the Plugin router $index before proceeding.
- Follow $critical-overrides.
- Refer to references/existing-codebase-edits.md for best practices on making edits to existing codebases.
User Context
Before starting, load $user-context and run its preflight script when local shell access is available.
Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material when relevant.
Do not inspect every saved reference. Inspect only what the current task needs.
Setup Is Not Prototype Work
If the user only asks to set up Product Design, do not continue in this skill. Use $user-context.
Workflows
The following workflows support cloning, redesigning, extending, and building products from scratch. Choose the workflow that best matches the user's request, or use the skills as helpers if the request does not match one workflow cleanly.
What ships with it
14 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/browser-order.md 387 B
- references/communication-protocol.md 1.9 KB
- references/critical-overrides.md 6.0 KB
- references/existing-codebase-edits.md 963 B
- references/local-prototype-preflight.md 860 B
- scripts/bootstrap-prototype.mjs 3.5 KB runs code
- templates/prototype/.npmrc 40 B
- templates/prototype/AGENTS.md 646 B
- templates/prototype/index.html 296 B
- templates/prototype/package.json 381 B
- templates/prototype/src/App.jsx 60 B
- templates/prototype/src/main.jsx 242 B
- templates/prototype/src/styles.css 145 B
- templates/prototype/vite.config.mjs 280 B runs code
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 · 129 lines · 47 tokens per session scan A 8b581875fa51
product-design-prototype is a skill published in the GitHub repository AIDotNet/OpenCowork (634 stars, last pushed 5d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,518 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-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…