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 Dragoon0x/everything-design-taste --skill design-critiquegit clone --depth 1 https://github.com/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/design-critique)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/design-critique"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/design-critique/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/dragoon0x/everything-design-taste/design-critique"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/design-critique.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.00022 | $0.00691 |
| Opus 5 | $0.00011 | $0.00345 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
design-critique 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Critique
Giving Critique
The Framework
For every piece of feedback, hit three points:
- Observation — What you see (factual, not opinion)
- Impact — Why it matters (connects to goals, users, or principles)
- Direction — What to explore (not prescriptive, but generative)
Example:
- Observation: "The CTA is the same visual weight as the navigation links."
- Impact: "Users scanning the page won't know where to click first."
- Direction: "Try increasing the size or contrast of the CTA, or reducing the visual weight of the nav."
What Good Critique Sounds Like
- "I notice [observation]. How does that serve [the user/the goal]?"
- "This works well because [specific reason]. What if we pushed it further by..."
- "The hierarchy here reads as [X] before [Y]. Is that the intended priority?"
- "I'm drawn to [element], but I think it might compete with [other element]."
What Bad Critique Sounds Like
- "I don't like it" (not actionable)
- "Make it pop" (meaningless)
- "Can we try it in blue?" (prescriptive without rationale)
- "This is wrong" (no direction, pure criticism)
- "What if we added..." (solution before understanding the problem)
Critique Priority Order
- Strategy — Is this solving the right problem?
- Structure — Is the information architecture correct?
- Interaction — Does the flow make sense?
- Visual — Does it look right?
- Polish — Are the details refined?
Don't critique polish when the strategy is wrong.
Receiving Critique
How to Present Work for Critique
- State what you want feedback on (scope the conversation)
- Explain the constraints you're working within
- Share what you've already tried and why you moved past it
- Don't apologize for unfinished work (it's a critique, not a showcase)
How to Process Feedback
- Write it down before responding
- Ask clarifying questions ("Can you say more about what feels off?")
- Look for patterns (if 3 people mention hierarchy, it's a hierarchy problem)
- Separate "I don't prefer this" from "this doesn't work for users"
- You don't have to act on everything. But you should understand everything.
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 · 69 lines · 22 tokens per session scan A 1991256d684a
design-critique is a skill published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 691 once invoked, about $0.0001 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
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
auteur
Design and build complete web experiences from scratch — award-level product and marketing pages, cinematic scroll-directed sites where the page is directed like a film, and multi-screen products (app, dashboard, admin, settings, onboarding, docs site) built as one design system with every component, state and route…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…
global-toolbar-controls
Quick global settings — currency, language, region, units — belong in a persistent, low-profile location such as a header toolbar or footer. These controls are frequent but not primary, so they use small typography and stay out of the main content hierarchy. Use when designing global selectors, locale switchers, or…