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-yolo)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-yolo"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-yolo/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-yolo"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-yolo.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.10295 |
| Opus 5 | $0.00010 | $0.05147 |
| Sonnet 5 | $0.00004 | $0.02059 |
| Haiku 4.5 | $0.00002 | $0.01030 |
Grade A, and why
wp-yolo 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 today.
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 — 634 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP YOLO — Full-Site Demo → WordPress Theme
Convert a complete multi-page HTML demo into a working theme in one orchestrated pass,
reusing the plugin's existing build pipeline end to end. Run this AFTER /wp-create +
/wp-init have scaffolded the project. This command does not reimplement any builder —
it dispatches the wp-normalize agent once, then drives the existing commands/agents in
dependency order.
Step 1: Parse Arguments & Gate
Parse $ARGUMENTS:
- First non-flag word = path to the demo folder (required). Error and exit if missing,
or if the path is not a directory:
Error: A demo folder is required. Usage: /wp-yolo <path-to-demo-folder> [--yolo] [--careful] [--force] --yolo= no checkpoint at all (ingest → build → seed → finalize → report, hands-off).--careful= checkpoint after normalization AND a per-page confirm before each inner page's build in Phase 2.- default (neither flag) = a single checkpoint after normalization, then hands-off.
Read .claude/CLAUDE.md at the project root. If it does not exist, refuse:
Error: No .claude/CLAUDE.md found. Run /wp-init first to scaffold the project.
Then refuse to run twice. This command has no resume entrypoint: a second
run restarts at Step 2, re-dispatches wp-normalize, overwrites
demo/.yolo-manifest.json and rebuilds the theme over whatever has been hand-
corrected since. If the theme directory already holds built section template
parts, or .claude/CLAUDE.md records a completed run, stop:
Error: <theme> already contains a built section flow (<n> template parts).
/wp-yolo rebuilds from the demo and would overwrite work done since the first run.
Use the per-step commands instead: /wp-section, /wp-page, /wp-seed, /wp-finalize.
Pass --force only to deliberately discard the current build.
Accept --force to override, and on a successful run append a
## Workflow — DONE, do not re-run note to .claude/CLAUDE.md recording the
date and which steps completed.
Extract function prefix, theme slug, languages (primary + secondary), template
(basic|tailwind), CF plugin (scf|acf), and i18n strategy (suffix|polylang) —
needed by every downstream command.
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.
- today Changed · +6 lines e9f3b568f258
- 4d ago Changed · +9 lines 6cd551e3d052
- 6d ago Changed · +68 lines a82fc135fd59
- 9d ago First seen · 551 lines · 20 tokens per session scan A 1ba4ab31f485
wp-yolo 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 10,295 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.