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 mblode/agent-skills --skill product-designgit clone --depth 1 https://github.com/mblode/agent-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/mblode/agent-skills/product-design)<a href="https://agentmods.dev/skills/mblode/agent-skills/product-design"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/product-design/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/mblode/agent-skills/product-design"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/product-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00067 | $0.02662 |
| Opus 5 | $0.00034 | $0.01331 |
| Sonnet 5 | $0.00013 | $0.00532 |
| Haiku 4.5 | $0.00007 | $0.00266 |
Grade A, and why
product-design 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 2d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Design
Decide what the interface should do, then route who builds and verifies it: pick the right interaction, make scope and consequence clear, cover reality beyond the happy path.
- IS: the decision layer. From a brief, spec, mockup, intent, or existing UI: choose the interaction and control, name the object, scope, and consequence of each action, settle reversibility and the safeguard it implies, enumerate every reachable state, set resilience expectations, and require accessibility as task completion. It decides, then routes build, verification, and wording out.
- IS NOT:
- whether a feature deserves investment or fits the product: the external
product-judgmentskill from Brandwriter. - building or styling UI, visual direction, palettes, type:
ui-design. - auditing the built result (rendered quality, a11y markup, keyboard, layout, performance, React or Next code-level UX with a ship verdict):
ui-designAudit mode. - copy wording, persuasion, or AI-ism removal:
copywriting. - motion, gesture physics, or deep typography:
ui-animation,typography-audit. - whether an agentic feature earns trust:
ax-audit.
- whether a feature deserves investment or fits the product: the external
Routing boundary
product-design owns action semantics, scope, reversibility, and contested state choices. ui-design builds and styles those states. ui-animation owns timing, gestures, and measured motion. A routine missing loading or error state stays with the UI build; a gesture replacing a control needs a product decision and an accessible alternative before its physics.
Request modes
Resolve one mode from the user's verb and artifact before acting, then load that mode's references. references/rules.md loads in every mode: every finding cites a rule ID from it, and you cannot conclude that no rule governs a decision without the registry in front of you.
| Mode | Dispatch when the user asks for | Load (plus references/rules.md) |
|---|---|---|
| shape (default) | "design the flow for", "what control here", "how should this work", "is this the right pattern", a brief with no settled UI | references/product-judgment.md, references/surfaces.md |
| spec | "spec the right interaction", "define the expected states", judgment applied before or during a build | references/product-judgment.md, references/surfaces.md, references/naming-and-copy.md; route the build to ui-design |
| review | "review this flow for product correctness", "what's wrong with this UX decision", "is this the right interaction" | references/interface-quality.md |
| action | "what should this action affect", "should this be undoable", "do we need a confirm dialog", or reversibility is unsettled | references/naming-and-copy.md; route final wording to copywriting |
| harden | "make this resilient", "what breaks here", error, permission, offline, expiry, and destructive paths | references/surfaces.md, references/interface-quality.md, references/product-judgment.md |
What ships with it
7 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.
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.
- 2d ago Changed · +1 lines 06869498ef67
- 3d ago Changed · -39 lines · -118 tokens per session a247264e02e0
- 9d ago First seen · 152 lines · 185 tokens per session scan A 08308e2a96c5
product-design is a skill published in the GitHub repository mblode/agent-skills (106 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 2,662 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
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…
mermaid-visualizer
This skill should be used when a user asks to explain a complex idea, concept, or system architecture, or when a diagram would be helpful to visualize control flows, system architectures, data flows, state machines, sequence diagrams, or entity relationships.
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
spawn-reviewers
Spawn and collect the reviewer fleet at stage20spawnreviewers. Consumes spawn.json.spec (the authoritative spawn spec from derive-spawn-spec / derive-static-spec), resolves GRAPHPROJECT, builds per-agent prompts from the per-agent template + role suffixes (Bug Hunter A/B, Unified Auditor, Domain Critics, Impact…
verify-findings
Dispatch and collect the finding-verifier fleet at stage23verifyfindings (PLN-722). Reads verifymanifest.json (written by stage22bverifyprepare), spawns one falsify-oriented verifier Task per toverify[] entry with mode-specific Task scheduling (GitHub mode dispatches verifiers synchronously; local mode uses parallel…