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 fmind/dotfiles --skill product-design-reviewgit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/fmind/dotfiles/product-design-review)<a href="https://agentmods.dev/skills/fmind/dotfiles/product-design-review"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/product-design-review.svg" alt="Measured on agentmods" 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.00047 | $0.00947 |
| Opus 5 | $0.00023 | $0.00474 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Design Review
Judge whether a real user can understand, trust, and complete the surface's primary job, then improve only what the requested scope authorizes.
Design Posture
- Identify the audience, context, and single job of the surface before discussing aesthetics.
- The brief and established product identity win. In Fmind work, use fmind-visuals for brand truth; do not replace Tokyo Night or existing tokens by habit.
- Classify the task as preserve, refine, or redesign. A critique does not authorize code edits, factual copy changes, or a new visual identity.
- Prefer one justified signature over decorative variety. Remove elements that do not encode meaning or help the task.
- Review real content, states, and runtime behavior. A static happy-path screenshot is insufficient.
- Bound iteration: one batched desktop/mobile review, one coherent fix pass when authorized, and one confirmation pass.
Workflow
- Recover product truth: Read the brief, existing product or design artifacts, tokens, components, user research, and representative content. Name any missing evidence.
- Map the journey: Identify entry points, primary action, decisions, exits, failure recovery, and time to first value.
- Inspect the live surface: Use quality-assurance to capture desktop and mobile states, DOM semantics, console/network errors, keyboard behavior, focus, reduced motion, and screenshots when a runnable app exists.
- Review comprehension: Check information architecture, hierarchy, labels, vocabulary, affordances, progressive disclosure, cognitive load, and whether the next action is obvious.
- Review every state: Cover first run, loading, empty, partial, success, validation, permission, error, offline, destructive confirmation, and recovery states that apply.
- Review craft: Evaluate typography, spacing, alignment, color, contrast, density, imagery, motion, consistency, and relationship to the subject. Flag generic defaults only when they weaken the brief.
- Review inclusion: Check semantic structure, keyboard access, focus visibility and restoration, touch targets, zoom/reflow, screen-reader names, contrast, motion preferences, localization, and plain-language copy.
- Review constraints: Identify performance, browser, device, content-length, data-density, privacy, and implementation constraints that change the design recommendation.
- Prioritize: Rank findings by blocked task, trust or accessibility harm, frequency, and effort. Recommend the smallest coherent improvement before aesthetic extras.
- Verify authorized changes: Re-run the same representative states at desktop and mobile sizes and record evidence without entering an unbounded polish loop.
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 · 55 lines · 47 tokens per session scan A cbca2160106b
product-design-review is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 947 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-31.
Other skills, from other repositories
product-design-review
Critique customer interfaces with runtime evidence across interaction, visuals, responsive behavior, accessibility, and content. Use for UX audits or redesigns.
mermaid
Create, theme, validate, and embed Mermaid diagrams, the default diagram format for GitHub and Markdown documentation. Use for any new diagram unless D2 or LikeC4 applies.
modern-web
Apply modern web platform standards, native HTML, CSS, and JavaScript features, and compatibility guidance. Use for modern web development, APIs, or front-end modernization.
d2
Create, theme, validate, and export D2 diagrams when an existing D2 source or a bespoke standalone composition beats the default Mermaid workflow.
fmind-visuals
Apply the Fmind visual identity and route decks or diagrams to Typst, Mermaid, or D2. Use for Fmind talks, decks, article diagrams, and site assets.
fkf-use
Use an fkf base safely: inspect status, retrieve bounded context, resolve URIs, traverse relations, collect sources, or serve read-only MCP. Use for read or collection workflows.