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 Dragoon0x/taste-skills --skill type-systemsgit clone --depth 1 https://github.com/Dragoon0x/taste-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/dragoon0x/taste-skills/type-systems)<a href="https://agentmods.dev/skills/dragoon0x/taste-skills/type-systems"><img src="https://agentmods.dev/badge/skills/dragoon0x/taste-skills/type-systems/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/dragoon0x/taste-skills/type-systems"><img src="https://agentmods.dev/badge/skills/dragoon0x/taste-skills/type-systems.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.00035 | $0.00435 |
| Opus 5 | $0.00017 | $0.00217 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
type-systems 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.
What it actually says
Type Systems
Typography is a system. Every decision should be intentional and connected.
How to use
/type-systemsApply type system constraints to this conversation.
Constraints
Scale
- MUST use a mathematical ratio for the type scale (1.25, 1.333, 1.5 between sizes)
- Wide range (12px to 72px): dramatic hierarchy, suits editorial and marketing
- Narrow range (14px to 24px): subtle hierarchy, suits dense products
- NEVER use random sizes. If it's not on the scale, it shouldn't exist.
- MUST limit to 4-6 sizes per screen maximum with clear justification for each
Weight
- 1-2 weights: discipline. Hierarchy comes from scale and space, not weight.
- 3 weights: normal range. Regular body, medium emphasis, bold headlines.
- 4+ weights: either the system demands it or you haven't made a decision.
- MUST ensure each weight serves a distinct, named purpose
Line Height
- Body text: 1.5-1.7x font size. Where readability lives.
- Headlines: 1.1-1.3x. Large text has built-in breathing room.
- UI labels: 1.2-1.4x. Compact but not crushed.
- NEVER use the same line height for all text sizes
Letter Spacing
- Body text: leave it alone. The type designer already optimized it.
- All-caps labels: add 2-5% tracking. Capitals need air.
- Large display text (72px+): sometimes benefits from tightening.
Anti-Patterns
- More than 3 type sizes on a single screen without clear hierarchy justification
- Centering paragraphs longer than 3 lines
- Lines over 75 characters wide (hurts readability)
- Inconsistent weight usage with no system behind it
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 · 45 lines · 35 tokens per session scan A 4e7755652e3c
type-systems is a skill published in the GitHub repository Dragoon0x/taste-skills (4 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 435 once invoked, about $0.0002 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
create-workflow-diagram
Create FigJam/Miro-style workflow diagrams as high-quality PNG images from plain-text workflow descriptions. Renders beautiful HTML diagrams with connected nodes, arrows, and labels, then screenshots them for sharing.
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
ui-designer/design-system
A shared set of rules for a product’s visual design, covering colors, fonts, spacing, corner shapes, shadows, and animations.
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.