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 lenar-amirov/product-pipeline-public --skill design-critique-templategit clone --depth 1 https://github.com/lenar-amirov/product-pipeline-publicWrote 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/lenar-amirov/product-pipeline-public/design-critique-template)<a href="https://agentmods.dev/skills/lenar-amirov/product-pipeline-public/design-critique-template"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/design-critique-template/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/lenar-amirov/product-pipeline-public/design-critique-template"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/design-critique-template.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.00069 | $0.00581 |
| Opus 5 | $0.00034 | $0.00291 |
| Sonnet 5 | $0.00014 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
design-critique-template 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 12d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Critique (hypothesis-first)
Critique for the /sketch → design loop (step 9). The order matters: a
beautiful screen that doesn't implement the hypothesis mechanism fails the
review regardless of heuristics.
1. Hypothesis fit — the first and decisive pass
Load the solution hypotheses this design serves (registry solutions links
output/solution-hypotheses.md):
- Does each screen implement the mechanism from the hypothesis formula ("if X then Y because Z" — is Z actually on the screen)?
- Did anything essential from
output/solution-sketch.mdget lost or mutated on the way to the mockup? Name the deltas. - Does the design add scope no hypothesis asked for? (scope creep enters through mockups more often than through PRDs)
2. Heuristic pass (classic, kept short)
- Visibility & hierarchy: is the primary action of each screen unmistakable in 5 seconds?
- User control: reversibility, escape routes, no dead ends
- Consistency: platform conventions and the product's own patterns (see ui-pattern-library — novelty only where novelty IS the hypothesis)
- Error prevention & recovery: empty states, loading, failure paths — the states mockups always forget
- Recognition over recall: labels over icons-only, context over memory
3. Feedback format
Per issue: screen → what breaks (hypothesis-fit or heuristic, name which) → severity (blocker / major / minor / polish) → concrete suggestion. Blockers first. Praise what works — reviewers who only list defects train designers to hide work.
4. Output
Update output/solution-sketch.md (## Changelog section) with accepted
changes; unresolved disagreements go to decisions.md as open questions.
If the critique overturns a solution assumption — that's registry news:
flag it to the PM (hypotheses.py set <id> --note ...), don't bury it in
design comments.
Anti-patterns
- Critiquing taste ("I'd make it blue") instead of hypothesis fit and heuristics — unfalsifiable feedback teaches nothing.
- A defect list with no severity — the designer can't sequence fixes.
- Reviewing the mockup without opening the solution hypothesis — you'll approve a beautiful screen that tests nothing.
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.
- 12d ago First seen · 56 lines · 69 tokens per session scan A 93fdf7b9cca2
design-critique-template is a skill published in the GitHub repository lenar-amirov/product-pipeline-public (12 stars, last pushed 23d ago), licensed MIT. It adds 69 tokens to every session and 581 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
presentation-design
Designs slide decks and one-pagers that carry an argument rather than decorate one — deck structure, headlines that state the takeaway, charts that make a single point, and the different rules board decks and conference talks follow. Use this to build or fix a pitch deck, board deck, or conference talk, to design a…
ux-product-auditor
Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to…
design-styles
Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions…
design-system
Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three…
interface-craft
Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or…
visual-content
Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals…