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 commands/muminur/frontend-design-craft-skill/typesetgit clone --depth 1 https://github.com/Muminur/frontend-design-craft-skillWrote 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/commands/muminur/frontend-design-craft-skill/typeset)<a href="https://agentmods.dev/commands/muminur/frontend-design-craft-skill/typeset"><img src="https://agentmods.dev/badge/commands/muminur/frontend-design-craft-skill/typeset.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 | $0.00012 | $0.00545 |
| Opus 5 | $0.00006 | $0.00272 |
| Sonnet 5 | $0.00002 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
typeset 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 4d 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.
What it actually says
/typeset
Diagnose and fix typography problems specifically. Do not touch layout, color, or motion unless they are blocking a typographic fix.
Target
$ARGUMENTS
Procedure
- Identify the current type system. What fonts are loaded? What sizes appear? What weights? Are there arbitrary
font-sizevalues? - Determine mode (brand or product) — this dictates whether to use fluid or fixed type scales.
- Replace generic font choices. If
Interis the default sans without justification, propose a substitute appropriate to the archetype:- Editorial/restrained: Geist, Söhne, IBM Plex Sans
- Soft/premium: General Sans, Cabinet Grotesk + Fraunces
- Brutalist: Helvetica, Departure Mono
- Expressive: Cabinet Grotesk, PP Editorial New
- Technical: Geist + Geist Mono
- Define a type scale as CSS variables or design tokens. Modular ratio ~1.2 for product, ~1.333 for marketing. Remove all arbitrary sizes.
- Calibrate line-height per size:
- Display 48px+ → 1.0–1.1
- H2 32–48px → 1.1–1.2
- H3 24–30px → 1.2–1.3
- Body 14–18px → 1.5–1.6
- Small 12–13px → 1.4–1.5
- Calibrate tracking:
- Display (48px+): -0.01 to -0.03em
- Body: 0 (default)
- All-caps labels: +0.05 to +0.1em
- Verify hierarchy. One primary heading per viewport, secondary level used 3–5 times, tertiary for body. Express via size+weight+color, not color alone.
Output
Before/after of the type system, summarized:
## Typeset complete
**Font stack:**
Before: [list]
After: [list]
**Type scale:**
[tokens]
**Line-height:**
[per size]
**Changes applied:**
- [list of files and what changed]
Ask the user to confirm the font choice before touching anything if there is real ambiguity about the archetype.
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.
- 4d ago First seen · 59 lines · 12 tokens per session scan A 899c5f7e1b77
typeset is a command published in the GitHub repository Muminur/frontend-design-craft-skill (4 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 545 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 commands, from other repositories
combo
Command "combo" from jiushiwon/wg-skills, covering 组合指令详解, 指令列表, icon-tag, badge and icon-btn.
ux-recommend
The v2 flagship. Runs the 5-parallel-search Python engine across 11 data manifests (75+ styles, 170+ palettes, 65+ type pairs, 120+ components, 170+ industries, 110+ UX laws, 50+ motion presets, 120+ anti-patterns, 92 brand specs) and returns a complete recommended design system for your project — with always-on…
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
designer
DaisyUI로 예쁜 UI를 만들거나, 기존 UI를 바꿔줘요.
design-system
Validate a project against the design-system guardrails — token-only styling, one component library, variants over call-site restyling. Reports drift by rule, and can fix it or scaffold the guardrails.