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/commands/yojahny55/claude-wp-builder/wp-demo)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-demo"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-demo/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/commands/yojahny55/claude-wp-builder/wp-demo"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-demo.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.00020 | $0.01893 |
| Opus 5 | $0.00010 | $0.00946 |
| Sonnet 5 | $0.00004 | $0.00379 |
| Haiku 4.5 | $0.00002 | $0.00189 |
Grade A, and why
wp-demo 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP Demo — HTML Mockup Generator
Create a standalone HTML demo for client approval that will later be converted section-by-section into WordPress templates.
Step 1: Read Project Context
Read .claude/CLAUDE.md to get the project name, slug, industry, description, and languages. If the file does not exist, tell the user to run /wp-init first.
Step 2: Get the Brief
Check $ARGUMENTS:
- If
$ARGUMENTSis "iterate": Read the existingdemo/index.htmlfile, then ask the user what changes they want. Apply changes and skip to Step 4. - If
$ARGUMENTSis provided (not "iterate"): Use it as the client brief. - If
$ARGUMENTSis empty: Ask the user for:- Client brief / description of what the site should look and feel like
- Reference screenshots or URLs (optional)
- List of sections to include (e.g., Hero, About, Services, Team, Testimonials, Contact)
Step 2.5: Choose the Demo Mode
Craft mode builds against the wp-demo-craft skill: a design floor, a page
grammar, a feeling curve with one peak, scroll motion via data-motion-*, and a
fingerprint gate so two clients never get the same shape. Plain mode is the
existing single-file demo with no motion contract.
Decide from the project, not from taste. Read .claude/CLAUDE.md (including
any Project Constraints section written by /wp-context), anything under docs/,
and .wp-create.json.
- Choose craft when the site is marketing, brand, launch, portfolio, agency or campaign work; when the docs name reference sites; or when they ask for motion, animation or a premium feel.
- Choose plain when the site is an admin tool, an intranet, catalogue- or data-heavy, regulated, or when the docs put accessibility first.
--craftand--plainin$ARGUMENTSoverride the decision. Honour them without arguing.
State the decision and the one-line reason for it. Then write it to
.wp-create.json as "demo mode": "craft" or "demo mode": "plain", creating the
key if absent. Every downstream command reads that line instead of deciding again.
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 · +62 lines fa1974ee32bb
- 10d ago First seen · 98 lines · 20 tokens per session scan A 4540f77e90d9
wp-demo is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,893 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.
Other commands, from other repositories
accessibility-specialist
Use when a screen might fail WCAG. Unlabeled inputs, no keyboard path, contrast below AA, missing landmarks, broken heading order, screen reader gaps, or a request for an a11y review or EU Accessibility Act check.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
conversational-ui-designer
Use when designing a chat or assistant interface. Message layout, bot personality, streaming and typing states, rich message cards, error recovery, or voice input.
form-designer
Use when a form is losing people. Too many fields, validation that interrupts typing, unclear required fields, a multi-step flow with no sense of progress, or inputs with no labels.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
spacing-layout-specialist
Use when spacing looks arbitrary. Padding and margins off any scale, inconsistent gaps between the same components, no grid underneath, or a layout that needs a denser mode.