wp-tailwindify

wp-tailwindify is a command for Claude Code from yojahny55/claude-wp-builder. It costs 23 tokens per session (2,769 once invoked), scanned A, original, MIT.

A command that converts a standard HTML/CSS demo into HTML using Tailwind CSS, a utility-class styling system. It preserves section markers and maps colors to Tailwind theme variables.

In plain words
What is it for?
Use it to convert a demo file into Tailwind-native HTML, optionally choosing the input and output paths. It looks for demo/index.html when no input file is supplied.
Why use it?
It removes the need to rewrite the demo's markup by hand for Tailwind. It can also write the result to a separate file or replace the input file when a backup exists.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

Part of the claude-wp-builder plugin — 15 skills, 28 commands, 15 agents shipped together

Install

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.

agentmods
npx agentmods add commands/yojahny55/claude-wp-builder/wp-tailwindify
Clone the repo
git clone --depth 1 https://github.com/yojahny55/claude-wp-builder

Made for: Claude Code.

Or install claude-wp-builder, the plugin that ships this one along with the rest of its 15 skills, 28 commands, 15 agents.

Wrote 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.

agentmods badge for wp-tailwindify

README.md
[![agentmods](https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-tailwindify.svg)](https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-tailwindify)
Your own site
<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-tailwindify"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-tailwindify.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.02769
Opus 5 $0.00012 $0.01385
Sonnet 5 $0.00005 $0.00554
Haiku 4.5 $0.00002 $0.00277

Measured 6d ago against content hash 5c56f034b2a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

wp-tailwindify 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 6d 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.

commands/wp-tailwindify.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

WP Tailwindify — Convert Demo to Tailwind

Convert a standard HTML/CSS demo file into Tailwind-native HTML.

Step 1: Locate the Demo File and Resolve the Output Path

Parse $ARGUMENTS:

  • First non-flag word = the input demo file.
    • If it is provided and is a file path, use that file.
    • Otherwise, check for demo/index.html in the current working directory.
    • If no demo file found, ask the user for the path.
  • --out <output-path> = where to write the converted HTML (optional). When omitted, the output path defaults to <demo-dir>/index-tailwind.html — the original behavior, unchanged for standalone/manual use.

--out may name the input file itself. That is a deliberate in-place conversion: the caller is responsible for having kept a backup first (this is how /wp-yolo Step 2.6 uses the command — it copies demo/<slug>.html to demo/.original/<slug>.html and then converts demo/<slug>.html onto itself, so every downstream reader that names demo/<slug>.html picks up Tailwind-native markup with no argument change).

Verify the input file exists and is an HTML file.

Step 2: Read and Validate

Read the demo HTML file. Check:

  • Is it already Tailwind-native? Absence of <style> blocks does not settle that — a plain-CSS demo can keep every rule in a linked stylesheet. Count a <style> block, a static style=" attribute or a <link rel="stylesheet"> pointing at a project-local .css file as plain CSS to convert. Treat the demo as already Tailwind-native only on positive evidence: class attributes that are predominantly Tailwind utilities (flex, px-4, text-lg, md:) and no project stylesheet. If it is ambiguous, convert — confirm with the user first when running standalone.
  • Does it have section delimiters? (Warn if missing — suggest running /wp-polish first.)

Step 3: Dispatch Conversion Agent

Dispatch the wp-tailwind agent (@agents/wp-tailwind) with the following context. The temp-path contract belongs in the context you actually hand the agent, not only in the paragraph below it — an agent that only reads these bullets must still get it right.

Read the full file on GitHub · 180 lines

Changes

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.

  1. 6d ago First seen · 180 lines · 23 tokens per session scan A 5c56f034b2a6

Subscribe to this mod's changes

wp-tailwindify is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 2,769 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-31.