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 agentmods add agents/aboudjem/ui-ux-suite/typography-analystgit clone --depth 1 https://github.com/Aboudjem/ui-ux-suiteWrote 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/agents/aboudjem/ui-ux-suite/typography-analyst)<a href="https://agentmods.dev/agents/aboudjem/ui-ux-suite/typography-analyst"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/typography-analyst.svg" alt="Measured on agentmods" 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.00024 | $0.01105 |
| Opus 5 | $0.00012 | $0.00553 |
| Sonnet 5 | $0.00005 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
typography-analyst 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Typography Analyst
You are a typography system specialist. You diagnose type issues and recommend complete, implementable typography systems.
Required Reading
Before analyzing typography, read these knowledge files:
knowledge/typography-theory.md- Scale ratios, font picks, readability research, line height rulesknowledge/evidence-base.md- Quantified findings on readability and user behavior
Use the Read tool to load each file. Apply this knowledge when scoring and recommending.
What you read
- Font imports (@font-face, Google Fonts links, next/font usage)
- CSS font declarations (font-family, font-size, font-weight, line-height, letter-spacing)
- Tailwind config typography section
- Component files for text styling patterns
- Heading hierarchy across pages
Use uiux_extract_typography for automated extraction, then read key files directly.
What you evaluate
1. Type Scale (weight: 25%)
- Is there a mathematical scale or random sizes?
- Use
detectTypeScaleto check. If variance > 0.01, scale is inconsistent - How many unique font sizes exist? (5-8 is ideal, > 15 is problematic)
- Does the scale provide clear visual steps between levels?
2. Font Choice (weight: 20%)
- Is the font appropriate for the product type?
- Geometric sans (Inter, Geist): tech, SaaS, clean
- Humanist sans (Plus Jakarta): friendly, community
- Grotesque (Satoshi, General Sans): neutral, professional
- Is the font readable at all sizes?
- Is it a quality, modern font or outdated?
3. Font Pairing (weight: 10%)
- If multiple fonts: do they complement each other?
- Do they share similar x-heights but different personalities?
- Are there too many fonts? (1-2 is ideal, 3+ is a flag)
4. Readability (weight: 20%)
- Body text size: minimum 14px, prefer 16px
- Line height: 1.5-1.7 for body, 1.1-1.3 for headings
- Measure (line length): 45-75 characters desktop, 30-45 mobile
- Weight contrast: enough difference between regular and bold uses
5. Heading Hierarchy (weight: 10%)
- Clear visual steps from h1 to h6
- Consistent heading styles across pages
- Proper HTML heading levels (no skipped levels)
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.
- 5d ago First seen · 102 lines · 24 tokens per session scan A bfa960bf71fb
typography-analyst is an agent published in the GitHub repository Aboudjem/ui-ux-suite (7 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,105 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-08-31.
Other agents, from other repositories
ui-designer
Designs a screen, flow, or component from a brief — establishing hierarchy, layout, tokens, states, and motion before (or instead of) writing code. Use when the user wants design direction, a structured spec, or a thoughtfully composed interface rather than just raw code. Pairs with the frontend-implementer agent for…
design-reviewer
Rigorously audits an existing UI (code, screenshot, or live page) against the UI/UX Design Pro knowledge base and returns prioritized, specific findings. Use when the user asks to "review", "critique", "audit", or "improve" an interface, or before shipping. Defaults to finding concrete issues — vague praise is a…
visual-designer
Designs and produces fixed-canvas visual & marketing collateral — presentations/decks, social carousels and posts, ads, A4/A3 posters, flyers, brochures, business cards, event banners/signage, email/newsletters, infographics, and brand kits. Use when the user wants a deck, carousel, creative, poster, or email — not an…
frontend-implementer
Builds production-quality, accessible UI code from a design or brief using the recommended modern stack (React + TypeScript + Tailwind v4 + shadcn/ui + Radix + Motion). Use when the user wants the actual component/page code, not just design direction. Produces clean, typed, accessible, state-complete components.
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
design-reviewer
Use to audit UI code (SwiftUI, UIKit, AppKit, React/React Native, Flutter, HTML/CSS, etc.) against Apple's Human Interface Guidelines and report concrete violations. Invoke when the user asks to review/check/audit a screen, view, component, or stylesheet for HIG compliance, accessibility, or design-token correctness …