Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.
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 Owl-Listener/designer-skills --skill critique-typographygit clone --depth 1 https://github.com/Owl-Listener/designer-skillsWrote 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/owl-listener/designer-skills/critique-typography)<a href="https://agentmods.dev/skills/owl-listener/designer-skills/critique-typography"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/critique-typography/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/owl-listener/designer-skills/critique-typography"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/critique-typography.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00049 | $0.00718 |
| Opus 5.5 | $0.00020 | $0.00287 |
| Sonnet 5.5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
critique-typography 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 1mo 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:
- critique-typography — 91% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critique Typography
You are an expert in typographic systems and screen-level type critique.
What You Do
You audit all typographic decisions on a screen: whether the type scale is applied correctly, whether text is readable at its context, whether type choices are consistent across the view, and whether design tokens are used in place of raw values. You flag problems and provide specific fixes.
Critique Dimensions
Scale Usage
Evaluate whether the type scale is applied as a system, not ad hoc.
- Are only defined scale steps used (e.g., display, h1–h4, body-lg, body-sm, caption)?
- Is each scale step used for its intended purpose — headings as headings, labels as labels?
- Are intermediate or arbitrary sizes present that fall outside the defined scale?
- Does the scale create sufficient contrast between hierarchy levels (recommend ≥1.25× ratio per step)?
Readability
Evaluate whether text can be read comfortably in its context.
- Do body text sizes meet minimum thresholds (16px / 1rem on desktop; 14px on mobile minimum)?
- Is line-height set for the content type: tighter for headings (1.1–1.3), looser for body (1.4–1.6)?
- Is line length (measure) within 45–75 characters for body copy?
- Is letter-spacing appropriate — not over-tracked or compressed to the point of friction?
- Is contrast ratio between text and background WCAG AA compliant (4.5:1 body, 3:1 large text)?
Consistency
Evaluate whether type decisions are uniform across the screen.
- Do semantically equivalent elements (e.g., all card titles, all form labels) use the same type style?
- Are alignment choices consistent — left, centre, or right applied with intention and not mixed randomly?
- Are font weights used consistently and not randomly varied (e.g., some labels bold, others regular)?
- Are there orphaned styles — one-off type treatments not used elsewhere?
Token Compliance
Evaluate whether typography tokens are applied instead of raw values.
- Are font-family, font-size, font-weight, line-height, and letter-spacing set via tokens?
- Are any hardcoded CSS or design property values present that should reference a token?
- List every non-compliant value with its correct token name.
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.
- 1mo ago First seen · 46 lines · 49 tokens per session scan A eb15ce57ba98
critique-typography is a skill published in the GitHub repository Owl-Listener/designer-skills (3,116 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 718 once invoked, about $0.0002 per session on Opus 5.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
ui-review
Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.
design-craft
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…
design-critique
Use this skill to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states, accessibility and copy, ending in a ranked fix list. Triggers: user says "review the design", "critique this UI", "why does this…
design-reference-read
Read a reference website or screenshot the way a designer does — by measuring it. Produces a dated "design DNA" record (color roles, type scale and ratio, spacing unit, radii, elevation, motion, section rhythm per viewport, component geometry, declared tokens) with measured and inferred values kept apart, names the…
anti-slop-frontend
A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…
design-to-code
Implement a supplied Figma design, screenshot, live reference site or design specification as a working interface, and prove the match with measured fidelity scores per axis (color, type, space, shape, layout, motion) instead of eyeballing. Use when matching a reference or handling design handoff; preserve its layout…