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 skills/ruchernchong/claude-kit/tailwindnpx skills add ruchernchong/claude-kit --skill tailwindgit clone --depth 1 https://github.com/ruchernchong/claude-kitWrote 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/ruchernchong/claude-kit/tailwind)<a href="https://agentmods.dev/skills/ruchernchong/claude-kit/tailwind"><img src="https://agentmods.dev/badge/skills/ruchernchong/claude-kit/tailwind.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.00038 | $0.01520 |
| Opus 5 | $0.00019 | $0.00760 |
| Sonnet 5 | $0.00008 | $0.00304 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
tailwind 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 3d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Tailwind CSS expert enforcing industry best practices.
Note: Spacing principles (4px grid, gap preference, bottom-only) are defined in the design-system-helper agent. This skill enforces Tailwind-specific syntax.
Critical Rules
1. Spacing Direction: Bottom Only, Never Top
Rule: Never use mt-* or pt-* classes. Use mb-*, pb-*, or gap instead.
// BAD - top spacing
<div className="mt-4 pt-4">
// GOOD - bottom spacing or gap
<div className="mb-4 pb-4">
<div className="flex flex-col gap-4">
2. Use size-* for Equal Dimensions
Rule: When width and height are equal, always use size-* instead of separate h-* and w-*.
// BAD - redundant classes
<div className="h-8 w-8">
<div className="h-12 w-12">
<div className="h-full w-full">
<div className="w-6 h-6">
// GOOD - use size-*
<div className="size-8">
<div className="size-12">
<div className="size-full">
<div className="size-6">
Only use separate utilities when dimensions differ:
// Correct - dimensions are different
<div className="h-8 w-12">
<div className="h-full w-screen">
3. Mobile-First Responsive Design
Rule: Always write mobile-first, progressively enhancing for larger screens.
// BAD - desktop-first (shrinking down)
<div className="text-2xl md:text-xl sm:text-lg">
// GOOD - mobile-first (scaling up)
<div className="text-lg md:text-xl lg:text-2xl">
4. Prefer Logical Shorthands
// BAD - verbose individual sides
<div className="mt-4 mr-4 mb-4 ml-4">
<div className="pt-2 pb-2">
<div className="pl-4 pr-4">
// GOOD - use shorthands
<div className="m-4">
<div className="py-2">
<div className="px-4">
5. GPU-Accelerated Animations
// BAD - animating layout properties
<div className="transition-all hover:ml-4">
// GOOD - use transform (GPU accelerated)
<div className="transition-transform hover:translate-x-4">
6. Follow 8px Grid System
Rule: Use spacing classes that are multiples of 8px. This is the industry gold standard (Material Design, Apple HIG).
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.
- 3d ago First seen · 164 lines · 38 tokens per session scan A d7b290498af8
tailwind is a skill published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 1,520 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-09-01.
Other skills, from other repositories
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…