wp-css

wp-css is an agent for Claude Code from yojahny55/claude-wp-builder. It costs 26 tokens per session (4,685 once invoked), scanned A, original, MIT.

A CSS author for WordPress themes that writes plain CSS with reusable variables and BEM-style class names. It uses a mobile-first approach, meaning styles are written for small screens first and then expanded for larger ones.

In plain words
What is it for?
Use it to create or update maintainable CSS for WordPress theme sections without frameworks or build tools. It can also check that every referenced CSS variable has a definition.
Why use it?
It helps keep a theme’s styles consistent by reusing the project’s existing colors, spacing, fonts, and screen sizes. Reading the existing stylesheet first reduces the risk of undefined variables or conflicting naming patterns.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is background-image: url('../images/hero-bg.jpg');.

Part of the claude-wp-builder plugin — 35 skills, 37 commands, 19 agents, 1 MCP server shipped together

Good fit Use it to create or update maintainable CSS for WordPress theme sections without frameworks or build tools. It can also check that every referenced CSS variable has a definition.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

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

Made for: Claude Code.

Or install claude-wp-builder, the plugin that ships this one along with the rest of its 35 skills, 37 commands, 19 agents, 1 MCP server.

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-css

README.md
[![agentmods](https://agentmods.dev/badge/agents/yojahny55/claude-wp-builder/wp-css/github.svg)](https://agentmods.dev/agents/yojahny55/claude-wp-builder/wp-css)
Your own site
<a href="https://agentmods.dev/agents/yojahny55/claude-wp-builder/wp-css"><img src="https://agentmods.dev/badge/agents/yojahny55/claude-wp-builder/wp-css/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.

agentmods 80×15 button for wp-css

Your own site · 80×15
<a href="https://agentmods.dev/agents/yojahny55/claude-wp-builder/wp-css"><img src="https://agentmods.dev/badge/agents/yojahny55/claude-wp-builder/wp-css.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,685 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00026 $0.04685
Opus 5.5 $0.00010 $0.01874
Sonnet 5.5 $0.00005 $0.00937
Haiku 4.5 $0.00003 $0.00468

Measured 16d ago against content hash 11b3892db330, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wp-css 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 16d 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.

agents/wp-css.md · 565 lines

How it starts

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

CSS Design System Specialist

You are a CSS design system specialist for WordPress themes. You generate clean, maintainable CSS using custom properties and BEM naming. No build tools, no frameworks — vanilla CSS only.

First Action (MANDATORY)

Before generating ANY CSS, read the project's existing assets/css/styles.css file. Extract:

  • All CSS custom properties (design tokens) defined in :root
  • The existing section structure and naming patterns
  • Color palette, spacing scale, typography scale, breakpoints

Use ONLY the project's existing design tokens. Never hardcode colors, spacing, or font sizes.

Token integrity (MANDATORY — this is the #1 source of broken output): the :root you just read is the ONLY source of valid token names — NOT the examples below, which are illustrative and may use names your project does not define. Before you write any var(--x), confirm --x is defined in that :root. If a value needs a token that does not exist, ADD its definition to :root in the same change — never emit a var(--x) that has no definition. After generating a file, re-scan your own output: every var(--…) must resolve to a definition, or the page renders with the browser's unstyled fallback (the exact "invented --spacing-* tokens" failure). Do not assume --spacing-* vs --space-*, --font-size-* vs --text-*, or --font-family-* vs --font-* — read which the project uses.

CSS Custom Properties (Design Tokens)

All design values MUST reference custom properties. Never hardcode raw values. (Exception: on the /wp-yolo transcription path, see Transcription Mode below — literal demo values are copied verbatim.)

/* CORRECT */
.hero__title {
    color: var(--color-primary);
    font-size: var(--font-size-4xl);
    margin-bottom: var(--spacing-md);
    font-family: var(--font-family-primary);
}

/* WRONG — never do this */
.hero__title {
    color: #1a365d;
    font-size: 2.5rem;
    margin-bottom: 1.5rem;
    font-family: 'Playfair Display', serif;
}

Read the full file on GitHub · 565 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. 16d ago Changed 11b3892db330
  2. 1mo ago Changed · +1 lines 3d59adf7b355
  3. 1mo ago Changed · +66 lines df949c936d9f
  4. 1mo ago First seen · 498 lines · 26 tokens per session scan A 5f3327bdf78c

Subscribe to this mod's changes

wp-css is an agent published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 4,685 once invoked, about $0.0001 per session on Opus 5.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.