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 sleeyax/promptfiles --skill tailwind-v3-compatgit clone --depth 1 https://github.com/sleeyax/promptfilesWrote 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/sleeyax/promptfiles/tailwind-v3-compat)<a href="https://agentmods.dev/skills/sleeyax/promptfiles/tailwind-v3-compat"><img src="https://agentmods.dev/badge/skills/sleeyax/promptfiles/tailwind-v3-compat/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/sleeyax/promptfiles/tailwind-v3-compat"><img src="https://agentmods.dev/badge/skills/sleeyax/promptfiles/tailwind-v3-compat.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.00048 | $0.02338 |
| Opus 5 | $0.00024 | $0.01169 |
| Sonnet 5 | $0.00010 | $0.00468 |
| Haiku 4.5 | $0.00005 | $0.00234 |
Grade A, and why
tailwind-v3-compat 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind v3 Compat
The v4 upgrade guide documents seven behavior changes that ship with an official "add this to your CSS to preserve the v3 behavior" snippet. This skill walks the user through all seven, then writes (or removes) each one in the project's Tailwind v4 entry CSS under marker comments.
This is a toggle, not an install: it is safe to re-run any time to flip a flag back.
Hard rules
- Never write without an explicit user choice. Every gate — entry-file pick, flag selection, container padding, apply confirmation — is a real stop: ask, then wait for the answer. Use the
AskUserQuestiontool when it's available in the session; where it isn't (e.g. Codex), ask in plain text with the same numbered options and stop until the user replies. Never assume an answer. Selecting nothing means writing nothing. - Walk through all seven flags, every run — both question groups, even if the user selected nothing in the first.
- Only touch marker-wrapped blocks. The entry CSS holds the user's own
@theme,@layer, imports, and plugin directives. Never reformat, reorder, or edit anything outside the markers. - Existing v4 setups only. Confirm the project is on Tailwind v4 before touching anything (step 1). If Tailwind is absent, still on v3, or has no entry CSS to edit, stop — this skill restores old defaults, it does not install or upgrade Tailwind.
- Never modify markup. Step 5 reports v3→v4 issues in components; it does not fix them.
Compat catalog
Each flag is written between /* tailwind-v3-compat:<id> */ and /* /tailwind-v3-compat:<id> */, which is what makes it independently detectable and removable.
| Marker ID | Flag | v4 default | v3 behavior restored |
|---|---|---|---|
border-color |
Default border color | currentColor |
gray-200 |
ring |
Default ring width/color | 1px, currentColor |
3px, blue-500 ⚠️ |
placeholder |
Placeholder color | current text at 50% opacity | gray-400 |
button-cursor |
Button cursor | default |
pointer |
dialog-margin |
<dialog> margins |
reset to 0 |
auto (centered) |
hover |
Hover variant | only where the primary input supports hover | always applies |
container |
container utility |
no centering or padding | centered with padding |
What ships with it
1 file 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.
- 9d ago First seen · 162 lines · 48 tokens per session scan A 442e1423cc47
tailwind-v3-compat is a skill published in the GitHub repository sleeyax/promptfiles (2 stars, last pushed 10d ago), licensed MIT. It adds 48 tokens to every session and 2,338 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
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
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.