Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yojahny55/claude-wp-builder/plugin install claude-wp-builderWrote 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/yojahny55/claude-wp-builder/wp-tailwind-system)<a href="https://agentmods.dev/skills/yojahny55/claude-wp-builder/wp-tailwind-system"><img src="https://agentmods.dev/badge/skills/yojahny55/claude-wp-builder/wp-tailwind-system/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/yojahny55/claude-wp-builder/wp-tailwind-system"><img src="https://agentmods.dev/badge/skills/yojahny55/claude-wp-builder/wp-tailwind-system.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.00049 | $0.04779 |
| Opus 5 | $0.00024 | $0.02389 |
| Sonnet 5 | $0.00010 | $0.00956 |
| Haiku 4.5 | $0.00005 | $0.00478 |
Grade A, and why
wp-tailwind-system 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 4d 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP Tailwind System
Applies when the project's .claude/CLAUDE.md says Template: tailwind. For
template=basic, use wp-css-system instead — the two are mutually exclusive.
Decision ladder
Applied per element, in order. Stop at the first rung that holds.
- Tailwind utility classes in the markup. The default, always. A section whose styling is expressible as utilities produces no CSS file entry at all.
- Same utility group on ≥2 pages → semantic class in
utilities/site.css, defined with@apply. - Repeated within a single page only → semantic class in
components/<slug>.css, defined with@apply. - Raw CSS (no
@apply) only for what Tailwind cannot express:@keyframes,clip-path, exotic selectors, third-party plugin overrides.
"Repeated" means the same group appears 3+ times, or on 2+ distinct pages. A group used twice inside one section stays inline.
File layout
Exactly four directories are sanctioned under assets/css/src/tailwindcss/:
base, components, layouts, utilities. Never create a fifth.
The four are not all present in a fresh theme. Git cannot track an empty
directory, so the starter ships only the ones that already hold a file —
layouts/ in particular is absent until something writes into it. Any of the
four may be created when the first rule that belongs there is written, in the
same step as that rule. Creating one of the four is not creating a new
directory; a fifth name is, whatever it holds.
main.css @import "tailwindcss"; @plugin; @theme{…}; then the @import list
base/ resets and font-face
components/<slug>.css one per page/template: home, contact, services, 404, search, blog
components/buttons.css shared components
layouts/ header, footer, sidebar — only when a layout needs @apply rules
utilities/site.css utility groups repeated across ≥2 pages
utilities/wordpress.css WordPress core class overrides
utilities/animations.css animation helpers
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.
- 4d ago Changed · +54 lines 1ec3d5be726f
- 6d ago Changed · +139 lines 622c87cabe6d
- 9d ago First seen · 203 lines · 49 tokens per session scan A e66aea38d28b
wp-tailwind-system is a skill published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 4,779 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
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", or "vs best practices".
color-audit
Color-only audit that extracts, evaluates, and recommends improvements for the project's color system. Use when the user asks to audit colors, run a color review or color audit, fix their colors, or work on the color palette or color system.
theme-builder
Build a light/dark theme from scratch or improve an existing one, with a complete surface, text, and interactive color system. Use when the user asks to build or create a theme, use the theme builder, or set up a light and dark theme.
layout-audit
Layout and spacing audit covering grid, spacing consistency, density, and responsive behavior. Use when the user asks to audit the layout, run a layout audit or grid audit, review spacing, or fix their spacing.