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 PaulRBerg/agent-skills --skill tailwind-cssgit clone --depth 1 https://github.com/PaulRBerg/agent-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/paulrberg/agent-skills/tailwind-css)<a href="https://agentmods.dev/skills/paulrberg/agent-skills/tailwind-css"><img src="https://agentmods.dev/badge/skills/paulrberg/agent-skills/tailwind-css.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.00035 | $0.00706 |
| Opus 5 | $0.00017 | $0.00353 |
| Sonnet 5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
tailwind-css 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 7d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind CSS
Style within the installed Tailwind version, existing design tokens, component patterns, and product context.
Authority and Defaults
- Inspect package versions, CSS entrypoints, theme declarations, shared components, class-merging utilities, and nearby UI before editing. Those are authoritative.
- Apply this catalog's preferences only where the project is silent. Read references/coding-preferences.md for that fallback style.
- Prefer existing semantic tokens and components over arbitrary values, new colors, or one-off utilities.
- Preserve responsive states, interaction states, accessibility, and dark-mode conventions. Do not add decorative UI or redesign beyond the request.
- Use CSS Modules only when the behavior is materially clearer than utilities; preserve any project-specific Tailwind reference mechanism.
Routing
- For v4 configuration, migration, removed utilities, variables, gradients, or CSS-first directives, read
references/tailwind-v4-rules.mdafter confirming v4 is installed. - For version-specific behavior that may have changed, consult the current official documentation matching the installed version. Treat the local v4 reference as a decision checklist, not an exhaustive substitute for the docs.
- For component variants or slots with
tailwind-variants, readreferences/tailwind-variants.md. - For
tw-animate-css, readreferences/tw-animate-css.md. - For Tailwind ESLint integration, read
references/eslint.md.
Do not apply v4 syntax to an older project merely because this skill targets v4. Use documentation matching the installed version, and migrate only when the request includes migration.
Workflow
- Define the visual outcome and affected states from the request and product context.
- Reuse local tokens, spacing, typography, breakpoints, components, and variant conventions. Make the smallest class/config change that achieves the outcome.
- Keep class names statically detectable. When values select styles, map them to complete class strings and verify that Tailwind scans every relevant source location.
- Run the repository's relevant lint/type/build checks.
- Render the affected screen or component at representative viewport sizes and inspect it visually, including changed interaction and theme states. When JavaScript or a component library transforms markup, inspect the final DOM and verify that selectors and state behavior still match. Fix visible regressions before completion.
What ships with it
6 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.
- 7d ago First seen · 58 lines · 35 tokens per session scan A e71e381c3101
tailwind-css is a skill published in the GitHub repository PaulRBerg/agent-skills (70 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 706 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-30.
Other skills, from other repositories
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
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.
tailwindcss
Tailwind CSS v4 conventions — semantic design tokens for theme-safe styling, mobile-first responsive layouts, and v4-first utilities. Use when styling components or writing className utilities with Tailwind. Don't use for plain CSS, CSS-in-JS (styled-components, emotion), or other utility frameworks.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.