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/gaia-react/gaia/tailwindnpx skills add gaia-react/gaia --skill tailwindgit clone --depth 1 https://github.com/gaia-react/gaiaWhat 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.00078 | $0.01254 |
| Opus 5 | $0.00039 | $0.00627 |
| Sonnet 5 | $0.00016 | $0.00251 |
| Haiku 4.5 | $0.00008 | $0.00125 |
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 2d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind
units
Always use Tailwind units first. For custom values, always use rem, never px.
// BAD - tailwind units available but custom rem used
return <div className="p-[1.0625rem]" />;
// GOOD - uses tailwind units
return <div className="p-4.25" />;
tailwind-merge
Use tailwind-merge to concatenate class names in React components instead of template literals or array joins.
twJoin: for conditional class combinations (no override needed)twMerge: allow class override (merges conflicting utilities; perfect for setting default and optional classes)
Examples
import {twMerge, twJoin} from 'tailwind-merge';
// BAD, template literals with potential conflicts
return <span className={`bg-gray-500 ${isBlue ? 'bg-blue-500' : ''}`} />;
// GOOD - twJoin for conditional classes, but no override needed
return <span className={twJoin('bg-gray-800', isBlue && 'text-blue-500')} />;
// GOOD, twMerge for override, twJoin for conditional classes
return <span className={twMerge('text-white', isBlue && 'text-blue-500')} />;
The key distinction: use twMerge when a component accepts a className prop that should be able to override defaults, twJoin would leave both conflicting classes on the element, but twMerge resolves the conflict:
// twMerge enables callers to override component defaults
function Button({className}: {className?: string}) {
return (
<button
className={twMerge('bg-blue-500 px-4 py-2 text-white', className)}
/>
);
}
// bg-red-500 wins, twMerge removes the conflicting bg-blue-500
<Button className="bg-red-500" />;
Conditional classes
Pass falsy values directly to twJoin / twMerge, they're skipped.
// correct
twJoin('base', isActive && 'bg-blue-500', error && 'border-red-500');
// ternaries that produce two positive values are fine
twJoin('base', condition ? 'a' : 'b');
Don't wrap class lists in template literals to concatenate, pass each class as a separate argument. Template literals inside twJoin / twMerge are acceptable only when interpolating a pre-built string from a lookup table (e.g., ICON_POSITION[iconPosition] from a Record<string, string>).
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.
- 2d ago First seen · 124 lines · 78 tokens per session scan A 25c4d414c789
tailwind is a skill published in the GitHub repository gaia-react/gaia (22 stars, last pushed 2d ago), licensed MIT. It adds 78 tokens to every session and 1,254 once invoked, about $0.0004 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…
oil-motion
Design, implement, optimize, and explain interactive web animations driven by scroll, pointer, drag, touch, device orientation, audio, data, or component state. Use when a webpage needs responsive visual motion for products, interfaces, diagrams, characters, or scene transitions.
engram-dashboard-htmx
HTMX and templ interaction rules for the Engram dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI.