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 Uxcel-Lab/product-skills --skill typographygit clone --depth 1 https://github.com/Uxcel-Lab/product-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/uxcel-lab/product-skills/typography)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/typography"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/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/uxcel-lab/product-skills/typography"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/typography.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.00074 | $0.01755 |
| Opus 5 | $0.00037 | $0.00877 |
| Sonnet 5 | $0.00015 | $0.00351 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
ux-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 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Typography Skill
How this skill behaves (read first)
This is a generative skill. Typography has two default failure modes: bland (pick one safe font, no real scale or hierarchy) and over-expressive (multiple display faces, many weights/colors/cases stacked → cluttered and illegible). So this skill gates:
- Establish brand personality, content types, and medium — these drive the expressive choices worth making.
- Apply the always-true core — legibility, a clear scale/hierarchy, and restraint hold for any product.
- Make the typeface/pairing/scale choices deliberately — surface them as gated decisions tied to brand, not defaults.
Then hand off to the audits: accessibility (size, contrast, spacing), aesthetics (hierarchy, balance).
Step 0 — Establish context before choosing type
- Brand personality & expected aesthetics — what impression should it make, and what does the audience expect (a kids' app vs. a banking app demand opposite tone)?
- Content types — what kinds of text exist (display, headings, body, captions, labels)? This sizes the hierarchy.
- Medium — long-form reading vs. dense UI vs. marketing — changes the legibility/expressiveness balance.
- Language direction — LTR vs. RTL (drives default alignment).
State assumptions if proceeding without answers.
The always-apply core (true for any typography)
Readability & legibility (body text)
- Body ≥ 16px. Start the scale from body size (it occupies the most space), then size up/down.
- Line length 50–75 characters. Longer is hard to track; too short forces choppy eye movement.
- Line height ~150% of font size for body; larger sizes/widths need more.
- Paragraph spacing ≥ 1.5× line spacing (WCAG); separate ideas into digestible blocks.
- Left-align body text in LTR (right for RTL). Reserve center alignment for short elements (headlines, quotes, CTAs) — it slows reading and hurts users with cognitive/visual impairments.
- Design for scannability — ~79% of users scan, ~3% read word-by-word; hierarchy + spacing make scanning work.
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 · 110 lines · 74 tokens per session scan A 717f55ac4d77
ux-typography is a skill published in the GitHub repository Uxcel-Lab/product-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,755 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-31.
Other skills, from other repositories
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
interface-polish
Design-engineering micro-detail pass for interfaces that already work but feel unrefined. Applies concrete CSS/JS rules for hover/active/focus states, transition timing and easing, enter/exit animations, stagger patterns, layered shadows, border-vs-shadow elevation, nested border-radius, optical alignment, typography…
premium-hero-builder
Build premium, dark-themed hero sections and landing pages with cinematic video backgrounds, liquid glass morphism, editorial typography, and pixel-perfect specifications. Based on the Viktor Oddy methodology of detailed design prompts that produce agency-quality results from AI code generation. Use when building hero…
page-flow-cleanup-audit
A review process for cleaning up a user-facing page or feature flow by tracing where its data and states come from. It checks loading, empty, error, permission, and lifecycle behavior before removing unnecessary code.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
empty-states
Turn dead ends into moments that build trust and guide action. Covers zero-data screens, error recovery, loading states, and retention micro-copy. Use when handling empty dashboards, failed searches, or moments where users hit a wall.