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 lenxism/ives --skill design-critiquegit clone --depth 1 https://github.com/lenxism/ivesWrote 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/lenxism/ives/design-critique)<a href="https://agentmods.dev/skills/lenxism/ives/design-critique"><img src="https://agentmods.dev/badge/skills/lenxism/ives/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/lenxism/ives/design-critique"><img src="https://agentmods.dev/badge/skills/lenxism/ives/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.00116 | $0.01136 |
| Opus 5 | $0.00058 | $0.00568 |
| Sonnet 5 | $0.00023 | $0.00227 |
| Haiku 4.5 | $0.00012 | $0.00114 |
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 9d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Critique
The goal is specific, tangible observations — not vague feedback. Every observation includes: what you see, why it matters, and what it could be instead.
Step 1: Establish Context
Before diving in:
- What is this product/feature? Who uses it?
- What emotional or functional job is it doing?
- What platform? (iOS, web, Android — each has different standards)
- What's the intended quality bar? (MVP, production, premium?)
Step 2: First Impressions (30 seconds)
Look at it as a user would on first encounter:
- What's the immediate emotional reaction? Trust, confusion, delight, anxiety?
- Where does your eye go first? Is that the right place?
- Does this feel like it belongs on its platform?
- Does it meet the industry standard bar?
Step 3: Systematic Review — Four Lenses
Lens 1: Visual Design
Typography
- Is there a clear typographic scale with intentional hierarchy?
- Are headline and body fonts well-chosen for context?
- Limit to 3-4 type sizes maximum. More signals a lack of system.
- Are numbers using tabular figures where values change?
- Is letter-spacing appropriate? (Tighter for large display, looser for small caps)
Color
- Is color used intentionally, or scattered without purpose?
- Too many colors competing? Could you achieve the same with fewer?
- Sufficient contrast for readability?
- One clear accent color, or multiple vying for attention?
- Are grays consistent in hue? (All warm, all cool — not mixed randomly)
Spacing & Proportion
- Is padding balanced within containers?
- Are gaps between related elements tight enough to show relationship?
- Are gaps between unrelated sections large enough to show separation?
- Do containers feel proportionally balanced?
Visual Weight & Noise
- Are border strokes heavier than necessary?
- Are shadows muddy or crisp? Do they serve a purpose?
- Is there unnecessary visual containment?
- Are decorative elements earning their place?
Consistency
- Icon styles consistent? (Don't mix filled and outline)
- Stroke widths consistent across the interface?
- Corner radius language consistent and intentional?
- Dividers used consistently or arbitrarily?
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.
- 9d ago First seen · 135 lines · 116 tokens per session scan A 067b75fc86f8
design-critique is a skill published in the GitHub repository lenxism/ives (5 stars, last pushed 6mo ago), licensed MIT. It adds 116 tokens to every session and 1,136 once invoked, about $0.0006 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
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
make-resume
A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.