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 sanky369/vibe-building-skills --skill product-design-reviewgit clone --depth 1 https://github.com/sanky369/vibe-building-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/sanky369/vibe-building-skills/product-design-review)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/product-design-review"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/product-design-review/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/sanky369/vibe-building-skills/product-design-review"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/product-design-review.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.00161 | $0.02128 |
| Opus 5.5 | $0.00064 | $0.00851 |
| Sonnet 5.5 | $0.00032 | $0.00426 |
| Haiku 4.5 | $0.00016 | $0.00213 |
Grade A, and why
product-design-review 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 2mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Design Review
Review a product the way a strong design lead would: walk its real tasks, judge it against explicit heuristics, and deliver findings a team can act on tomorrow. Prime directive: evidence over opinion. Every finding names where it occurs, what the user suffers, and the concrete fix — and never claims to have seen something you didn't actually render. A review that says "improve the hierarchy" has failed; one that says "the destructive Clear action sits one unconfirmed click from the primary CTA (checkout.html:18) — gate it behind a confirm" has done its job.
When to use / when not
- Use for critique of an existing product surface: a page, flow, app, prototype, or design system in use.
- If the user wants the fixes implemented, deliver the review, then route each fix per the table in step 5 — don't rebuild the UI inside this skill.
- If the product's problem is the promise, not the pixels (nobody wants the thing), hand off to
skills/product-strategy/foundation-sprint. - If the user wants a broad "make it better" engagement rather than a review artifact, hand off to
skills/frontend-design/frontend-orchestrator.
Step 1 — Establish evidence mode
Before any judgment, determine what you can actually inspect. Pick the strongest mode available; state which one you're in at the top of the report.
| Artifact | Procedure | Evidence tier |
|---|---|---|
| Live URL + browser automation available (claude-in-chrome, agent-browser, Playwright) | Render it. Screenshot at ~375px and ~1440px. Tab through the primary flow checking focus visibility. Trigger reachable error, empty, and loading states. | Observed |
| Live URL, no browser | Fetch the HTML and CSS. You can verify markup semantics, labels, real color/type values, and compute contrast ratios. You cannot see layout, motion, or states — say so. | Computed |
| Codebase | Read the flow's components, styles, and copy. If the project documents a way to run the app, run it and review rendered output (upgrades findings to observed). | Computed |
| Screenshots / mockups | Visual, copy, and hierarchy critique of what's shown. Keyboard behavior, states, and motion are unverifiable — list them under "needs live check", don't guess. | Observed (static only) |
| Figma link | Use Figma MCP tools (get_screenshot, get_design_context) if connected; otherwise ask for exported frames. |
Observed (static only) |
What ships with it
1 file 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.
- 2mo ago First seen · 121 lines · 161 tokens per session scan A d5cc1c94e151
product-design-review is a skill published in the GitHub repository sanky369/vibe-building-skills (31 stars, last pushed 3mo ago), licensed MIT. It adds 161 tokens to every session and 2,128 once invoked, about $0.0006 per session on Opus 5.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.
product-design-review compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| product-design-reviewsanky369/vibe-building-skills | Skill | 31 | 3mo ago | MIT | A | 161 | Claude Code, Codex |
| planjeremylongshore/tons-of-skills-marketplace | Skill | 2.9k | yesterday | MIT | A | 144 | Claude Code |
| prototypevinvcn/mattpocock-skills-zh-CN | Skill | 5.6k | 9d ago | MIT | A | 39 | Claude Code, Codex |
| data-visualization-expertroedyrustam/vibes-plug | Skill | 121 | yesterday | MIT | A | 38 | Cursor |
| design-system-architectroedyrustam/vibes-plug | Skill | 121 | yesterday | MIT | A | 43 | Cursor |
| ephemeral-generative-ui-architectroedyrustam/vibes-plug | Skill | 121 | yesterday | MIT | A | 47 | Cursor |
| prototypedevcxl/mattpocock-skills-zh | Skill | 530 | 3d ago | MIT | A | 39 | Claude Code, Codex |