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 magnus919/agent-skills --skill product-design-and-uxgit clone --depth 1 https://github.com/magnus919/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/magnus919/agent-skills/product-design-and-ux)<a href="https://agentmods.dev/skills/magnus919/agent-skills/product-design-and-ux"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/product-design-and-ux/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/magnus919/agent-skills/product-design-and-ux"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/product-design-and-ux.svg" alt="Reviewed on agentmods" width="80" 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.00094 | $0.01147 |
| Opus 5 | $0.00047 | $0.00574 |
| Sonnet 5 | $0.00019 | $0.00229 |
| Haiku 4.5 | $0.00009 | $0.00115 |
Grade A, and why
product-design-and-ux 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Design and UX
Turn validated evidence and chosen scope into observable behavior people can complete and recover from. Design the interaction, not the brand, pixels, CSS, component implementation, or a particular tool.
Entry Check
Confirm the approved scope, outcome, users or roles, evidence links, constraints, measurable experience goals, and open product decisions. Record missing inputs rather than inventing them.
- Need stakeholder evidence, validation, or raw research? Use product-discovery.
- Need prioritization, scope, or why a feature is being built? Use product-methodology.
- Need WCAG, ARIA, native semantics, or accessibility testing depth? Use web-accessibility.
- Need an approved interaction contract translated into a software specification and delivery gates? Use spec-driven-development.
Workflow
- Trace each outcome and design decision to evidence with
templates/outcomes-to-design.md. Optional personas or jobs must change a decision and cite evidence; do not create decorative demographics. - Establish information architecture from goals, content objects, terminology, permissions, findability, and service context. Read
references/information-architecture.md. - Define consequential labels, instructions, status, errors, and completion content; review the task's memory, choice, switching, interruption, and recovery demands. Use heuristics to generate testable questions, not verdicts. Read
references/content-and-cognitive-demand.md. - Model important tasks, including forces that create decisions, alternatives, interruption, re-entry, cancellation, recovery, irreversible actions, side effects, permission changes, and completion evidence. Read
references/task-flows-and-state-models.mdand usetemplates/task-flow-state-model.md. - Inventory only states forced by the flow, data, permissions, connectivity, and risk. Record risky omissions. Use
templates/screen-state-inventory.md. - Write framework-neutral contracts for content, controls, accessible interaction requirements, actions, transitions, persistence, permissions, responsive/reflow behavior, telemetry, and open decisions. Read
references/interface-contracts-and-responsive-behavior.mdand usetemplates/interface-contract.md. - Treat patterns as hypotheses. Compare alternatives, tradeoffs, evidence, and disconfirming conditions with
references/interaction-pattern-selection.md. - Plan or synthesize only authorized usability work. Read
references/usability-testing-and-privacy.md; usetemplates/usability-study.md. Never invent participants, consent, observations, quotes, or results. - Produce an engineering handoff with observable acceptance evidence, dependencies, owners, gates, and deployed-boundary verification. Read
references/engineering-handoff.md; usetemplates/engineering-handoff.md. Hand approved behavior to spec-driven-development.
What ships with it
18 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.
- evals/evals.json 7.9 KB
- README.md 2.0 KB
- references/boundaries-and-traceability.md 1.9 KB
- references/content-and-cognitive-demand.md 4.1 KB
- references/engineering-handoff.md 4.1 KB
- references/information-architecture.md 3.2 KB
- references/interaction-pattern-selection.md 3.7 KB
- references/interface-contracts-and-responsive-behavior.md 3.7 KB
- references/scenario-probes.md 2.1 KB
- references/source-index.md 3.6 KB
- references/task-flows-and-state-models.md 1.6 KB
- references/usability-testing-and-privacy.md 4.5 KB
- templates/engineering-handoff.md 905 B
- templates/interface-contract.md 703 B
- templates/outcomes-to-design.md 627 B
- templates/screen-state-inventory.md 410 B
- templates/task-flow-state-model.md 737 B
- templates/usability-study.md 1.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.
- 9d ago First seen · 64 lines · 94 tokens per session scan A e93cbfb38ef3
product-design-and-ux is a skill published in the GitHub repository magnus919/agent-skills (76 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 1,147 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
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.
taiyi-diagram-arch
A workflow for turning written system or product architecture into readable, version-controlled diagrams using Mermaid or exported SVG and PNG files. Architecture diagrams show components, boundaries, data flows, and deployment relationships.
visual-design
A design skill for turning content into complete, self-contained HTML pages and visual materials such as websites, banners, posters, reports, resumes, and portfolios. It follows a defined visual design system and does not use outside images or code libraries.
taiyi-restyle
A planning guide for breaking a large user-interface redesign into smaller, independently reviewable tasks. A user interface is the part of an application that people see and use.
taiyi-diagram-pipeline
A pipeline that creates and updates architecture diagrams in three stages: a C4 model from the code, an engineering architecture diagram, and an exported PNG image. C4 is a way to describe software architecture at several levels of detail.
taiyi-diagram-render
A tool for rendering existing C4 or architecture Mermaid diagrams as SVG or PNG images. C4 is a way to show software systems at different levels, while Mermaid is a text format for diagrams.