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 wpank/ai --skill tailwind-v4-shadcngit clone --depth 1 https://github.com/wpank/aiWrote 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/wpank/ai/tailwind-v4-shadcn)<a href="https://agentmods.dev/skills/wpank/ai/tailwind-v4-shadcn"><img src="https://agentmods.dev/badge/skills/wpank/ai/tailwind-v4-shadcn.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.00011 | $0.02412 |
| Opus 5 | $0.00005 | $0.01206 |
| Sonnet 5 | $0.00002 | $0.00482 |
| Haiku 4.5 | $0.00001 | $0.00241 |
Grade A, and why
tailwind-v4-+-shadcn/ui-stack 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 8d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
13 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.
- commands/setup.md 4.1 KB
- README.md 1.9 KB
- references/architecture.md 4.2 KB
- references/common-gotchas.md 7.4 KB
- references/dark-mode.md 5.3 KB
- references/migration-guide.md 6.8 KB
- rules/tailwind-v4-shadcn.md 2.7 KB
- templates/components.json 396 B
- templates/index.css 4.5 KB
- templates/theme-provider.tsx 2.2 KB
- templates/tsconfig.app.json 719 B
- templates/utils.ts 166 B runs code
- templates/vite.config.ts 337 B runs code
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.
- 8d ago First seen · 384 lines · 11 tokens per session scan A b392449b798a
tailwind-v4-+-shadcn/ui-stack is a skill published in the GitHub repository wpank/ai (11 stars, last pushed 6mo ago), with no licence file. It adds 11 tokens to every session and 2,412 once invoked, about $0.0001 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-shiny-ui
Design Shiny application UIs using bslib for theming, layoutcolumns for responsive grids, value boxes, cards, and custom CSS/SCSS. Covers page layouts, accessibility, and brand consistency. Use when building a new Shiny app UI from scratch, modernizing an existing app from fluidPage to bslib, applying brand theming…
design-system
Use when establishing visual foundations for a new product, when defining design tokens, when building or auditing a component library, before any UI work begins on a fresh codebase, or when the existing UI has drifted into hex codes and magic numbers.
interaction-patterns
Use when deciding how users interact with UI elements — expand vs navigate, modal vs bottom sheet, swipe gestures, tap targets, optimistic UI, loading patterns, or undo for destructive actions. Use before features get built so every screen inherits the same rules.
page-composition
Use when defining how pages are assembled from components, when establishing layout grids, when deciding responsive collapse strategies, or when multiple routes have inconsistent layouts.
ai-core-web-vitals
A diagnostic assistant for Core Web Vitals, Google's measures of page loading speed, responsiveness, and visual stability. It is intended for technical, product, marketing, and software work.
ai-design-taste-frontend
A frontend visual-quality reviewer that examines whether an interface looks polished and coherent. It produces visual or creative diagnoses, prompt or storyboard ideas, and publishing checks.