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 Kevin-Liu-01/Agent-Machines --skill design-reviewgit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/design-review)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/design-review"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/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/kevin-liu-01/agent-machines/design-review"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 64 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00081 | $0.02260 |
| Opus 5 | $0.00041 | $0.01130 |
| Sonnet 5 | $0.00016 | $0.00452 |
| Haiku 4.5 | $0.00008 | $0.00226 |
Grade A, and why
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gstack-design-review — 89% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Review — Audit, Fix, Verify
Adapted from GStack v0.17.0.0 by Garry Tan. Uses agent-browser instead of
GStack's $B commands. UX principles from Steve Krug's "Don't Make Me Think."
Contract
This skill guarantees:
- Structured design audit with letter grades (A-F) across 10 categories
- AI Slop Score as standalone headline metric
- 6 usability tests on every page (Trunk Test, 3-Second Scan, Page Area Test, Happy Talk Detection, Mindless Choice Audit, Goodwill Reservoir)
- First-person narration mode (anti-slop: if you can't name the specific element, you're generating platitudes)
- Before/after screenshots for every fix
- One atomic commit per fix
- Findings sorted by impact (High > Medium > Polish)
UX Principles: How Users Actually Behave
The Three Laws of Usability
- Don't make me think. Every page should be self-evident. If a user stops to think "What do I click?" — the design has failed.
- Clicks don't matter, thinking does. Three mindless, unambiguous clicks beat one click that requires thought.
- Omit, then omit again. Get rid of half the words on each page, then get rid of half of what's left. Happy talk must die. Instructions must die.
How Users Actually Behave
- Users scan, they don't read. Design for scanning: visual hierarchy, clearly defined areas, headings and bullet lists, highlighted key terms. We're designing billboards at 60 mph.
- Users satisfice. They pick the first reasonable option, not the best. Make the right choice the most visible choice.
- Users muddle through. They don't figure out how things work. They wing it.
- Users don't read instructions. Guidance must be brief, timely, and unavoidable.
Billboard Design for Interfaces
- Use conventions. Logo top-left, nav top/left, search = magnifying glass. Don't innovate on navigation to be clever.
- Visual hierarchy is everything. More important = more prominent. If everything shouts, nothing is heard.
- Make clickable things obviously clickable. No relying on hover states for discoverability.
- Eliminate noise. Fix noise by removal, not addition.
- Clarity trumps consistency.
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 · 198 lines · 81 tokens per session scan A 7b402594a59d
design-review is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 2,260 once invoked, about $0.0004 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
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
omarchy-theme-maker
Use when an Omarchy desktop should be themed from a wallpaper or photo by deriving a contrast-checked colors.toml palette from the image, installing it as the theme background, and applying it with omarchy theme set.
kernelcad-authoring
Author or modify kernelCAD models in TypeScript. Scripts live in .kcad.ts files; the kernelCAD CLI (kernelcad evaluate and kernelcad export stl|step|dxf|3mf|glb -o ) executes them via an OpenCASCADE WASM kernel.
maya-primitives
Authoring stage — schema-validated quick path for creating polygon primitives and editing transforms. Use for predictable, agent-driven primitive creation; the parameters are validated by inputSchema and the results carry structured object names. For complex mesh editing use maya-mesh-ops, for materials use…
kernelcad-trace-from-image
Convert pixel-space features from a reference photo into normalized [0,1] waypoints, then into mm coordinates feedable to path().spline / path().nurbsSegment. Uses the tracefromimage MCP tool. Load when your blockout is in place and the next step is an organic-curve outline (eyewear brow, ergonomic handle, sneaker…
holix-cron
Schedule recurring agent tasks via Holix built-in gateway cron (not crontab or custom scripts).