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 jeremylongworth-source/AgentSkills --skill tailwind-design-systemgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/tailwind-design-system)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/tailwind-design-system"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/tailwind-design-system/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/jeremylongworth-source/agentskills/tailwind-design-system"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/tailwind-design-system.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.00066 | $0.00448 |
| Opus 5.5 | $0.00026 | $0.00179 |
| Sonnet 5.5 | $0.00013 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
tailwind-design-system 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.
What it actually says
Tailwind Design System
Core Workflow
- Identify Tailwind version, framework, styling architecture, component library, token source, and build setup.
- Inspect existing patterns before adding new utilities, colors, spacing, shadows, or radii.
- Define design tokens and component variants before one-off class strings multiply.
- Use complete static class names where Tailwind must detect utilities. Avoid dynamic string construction that the compiler cannot see.
- Keep responsive, state, dark-mode, and data/ARIA variants predictable.
- Verify production CSS generation and visual output in the browser.
Design System Priorities
- Tokens: colors, typography, spacing, radius, shadows, borders, z-index, motion, and breakpoints should be deliberate.
- Components: define variants for buttons, inputs, cards, nav, modals, tables, badges, alerts, and menus.
- Consistency: prefer shared component APIs or variant helpers over repeated ad hoc class clusters.
- Responsiveness: design mobile, tablet, and desktop behavior explicitly.
- Accessibility: preserve focus styles, contrast, hit targets, disabled states, and semantic HTML.
- Production: make sure Tailwind can detect classes and avoid shipping accidental unused CSS.
Freshness Rule
Tailwind CSS source detection and configuration changed significantly across versions. Verify current official Tailwind docs before giving version-sensitive guidance about config files, @source, content detection, plugins, or production CSS behavior.
Deliverable Shape
For Tailwind work, provide:
- Tailwind version and integration assumptions
- Token/component patterns found
- Source detection or build risks
- Refactor or design-system recommendations
- Accessibility and responsive-state checks
- Production CSS verification steps
References
- Read
references/tailwind-system-checklist.mdwhen auditing or refactoring Tailwind UI.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 45 lines · 66 tokens per session scan A 0ed1a7d75389
tailwind-design-system is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 66 tokens to every session and 448 once invoked, about $0.0003 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
static-web-artifacts-builder
Build self-contained static HTML artifacts opened in a browser: interactive diagrams, dashboards, infographics. Pure HTML5+CSS3+inline SVG, zero toolchain. Triggers on: "interactive HTML", "open in browser", "HTML artifact", "visual dashboard", "HTML infographic". NOT for PNG/SVG output, use concept-to-image. NOT for…
web-design-system-foundation
Use when the repository has no design system yet (no tokens, no component library - a new site/app, an "Apply design system" task, or a task that asks for one), before building any page section - writes the approved design system's generated files from getdesignsystem (files true) and builds the tokens on them when…
screen-mockup-html
Use when you draw a screen as HTML mockup documents (one per variant) - the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task.
responsive-layout
Use when you build or change a layout, page, section, navigation, table, form or image - mobile-first rules, breakpoints and the overflow traps.
accessibility-basics
Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs/menus, visible focus, and never color as the only signal.
web-design-direction-system
Resolve shared design intent and guidance.