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/legacybridge-tech/claude-plugins/tailwindplusnpx skills add legacybridge-tech/claude-plugins --skill tailwindplusgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWhat 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.00043 | $0.00663 |
| Opus 5 | $0.00022 | $0.00331 |
| Sonnet 5 | $0.00009 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
tailwindplus 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TailwindPlus Component Browser
This skill provides access to the TailwindPlus UI component library with 657+ professional components.
Setup Required
Before using this skill, you need to specify the location of your TailwindPlus JSON data file.
Tell Claude the path to your tailwindplus-components-*.json file and Claude will use it in the commands.
Example: "My TailwindPlus data is at ~/data/tailwindplus-components-2026-01-08.json"
Available Commands
All commands require the JSON data file path as the first argument.
Get Component Info
./info.sh <json_file>
Returns metadata about the TailwindPlus data file.
List All Components
./list_components.sh <json_file>
Returns all component names organized by category.
Search Components
./search_components.sh <json_file> "hero"
./search_components.sh <json_file> "pricing table"
Search for components by keyword (case-insensitive, supports multi-word).
Get Component Code
./get_component.sh <json_file> "Application UI.Forms.Input Groups.Simple" -f html -v 4 -m light
./get_component.sh <json_file> "Ecommerce.Components.Product Overviews.With image gallery and expandable details" -f react -v 4 -m none
Required Parameters:
json_file: Path to the TailwindPlus JSON data filefull_name: The complete dotted path (e.g., "Application UI.Forms.Input Groups.Simple")-f, --framework:html,react, orvue-v, --version:3or4(Tailwind CSS version)-m, --mode: Theme mode
Mode Requirements (CRITICAL):
- Application UI and Marketing components: use
light,dark, orsystem - eCommerce components: use
noneonly
Component Categories
- Application UI - Forms, navigation, data display, overlays, layout components
- Marketing - Hero sections, features, pricing, testimonials, CTAs, footers
- Ecommerce - Product lists, shopping carts, checkout forms, order history
Framework Options
html- Pure HTML with Tailwind CSS classesreact- React/JSX componentsvue- Vue.js components
What ships with it
4 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.
- 2d ago First seen · 82 lines · 43 tokens per session scan A 2e8cc185e468
tailwindplus is a skill published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 663 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
frontend-architecture
How to organize frontend code — separation of concerns (UI / logic / data / type), file responsibility, state tiers, API services, schema validation, and framework conventions for React/Next and Vue. Structural rules, not visual design.
tanstack-form
Headless, performant, and type-safe form state management for TS/JS, React, Vue, Angular, Solid, Lit, and Svelte.
livecodes/framework-wrappers
Use SDK with React, Vue, Svelte, Solid, Preact, and Web Components. sdkReady callback pattern, reactive props, and framework-specific setup. Load this skill when embedding LiveCodes in a framework application.
web-development
Use when users need to implement, integrate, debug, build, deploy, or validate a Web frontend after the product direction is already clear, especially for React, Vue, Vite, browser flows, or CloudBase Web integration.
create-component
End-to-end SEED component implementation guide for React Web, Lynx, and cross-platform work. Use when adding or changing components across rootage, qvism, react/lynx packages, registry snippets, docs, examples, or when writing/refactoring docs/stories Storybook files. Story-only work follows a CSF Next fast path…
seed-design
SEED Design 통합 가이드. 공통 컴포넌트 스펙과 파운데이션을 공식 문서에서 찾고, React·Lynx 프로젝트의 구현·설치·CLI·마이그레이션을 대상 플랫폼에 맞게 안내하며, 지원되는 플랫폼의 사용 상태를 Doctor로 진단한다. SEED Design 관련 질문, 컴포넌트 사용법, 색상·타이포·스페이싱, 셋업, 스니펫, 업그레이드, "잘 쓰고 있나?", "뭘 고쳐야 하나?" 같은 요청이면 이 스킬을 사용한다.