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-polish)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-polish"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-polish/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-polish"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-polish.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.00016 | $0.02838 |
| Opus 5 | $0.00008 | $0.01419 |
| Sonnet 5 | $0.00003 | $0.00568 |
| Haiku 4.5 | $0.00002 | $0.00284 |
Grade A, and why
wp-polish 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP Polish — Demo Normalizer
Normalize any HTML file into a plugin-compatible demo with section delimiters, semantic HTML5, and BEM class naming. Works with external HTML (Figma exports, hand-coded, other tools) or existing demos that need structural cleanup.
--craft (retrofit audit)
Read ${CLAUDE_PLUGIN_ROOT}/skills/wp-demo-craft/SKILL.md and audit the existing
demo against the refuse list and the taste floor. Report findings as a list, each
naming the rule and the offending selector or line. Do not add motion and do not
restructure the page; converting a plain demo to craft is a rebuild, not a
polish. The existing backup behaviour at demo/.prepolish/ is unchanged.
Step 1: Resolve Input Path
This step resolves paths and decides nothing else. It creates no directories and it puts no file anywhere, so the copy Step 2 takes really is the document as it stood before this command ran.
Check $ARGUMENTS:
- If
$ARGUMENTSis provided: use it as the path to the HTML file to polish — the source document.- If the path points to a file outside
demo/, the polished output is destined fordemo/index.html, and Step 6 createsdemo/when it writes there. Do not copy the source overdemo/index.htmlhere. Step 6 puts the polished result at that path anyway, and doing it early destroys the page already sitting there before Step 2 has preserved anything at all. - If the path points to a file inside
demo/that is notindex.html(e.g.,demo/pricing.html), polish it in-place — source and destination are the same file. Step 2 preserves the pre-polish copy underdemo/.prepolish/(e.g.,demo/.prepolish/pricing.html), never beside the demo pages.
- If the path points to a file outside
- If
$ARGUMENTSis empty: Default todemo/index.html, as both source and destination. If the file does not exist, tell the user to provide a path or create a demo first with/wp-demo.
Step 2: Preserve the Source Document
Save a copy of the source document under demo/.prepolish/ before anything is written:
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 · +8 lines 21a67d5c5ba0
- 9d ago First seen · 204 lines · 16 tokens per session scan A e2eebb1be08f
wp-polish is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 2,838 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
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.
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.
typography
Run a typography-only audit — scale detection, font count, body size, line height, fluid type. Scoped variant of /ui-ux-suite:audit.
dark-mode-specialist
Use when dark mode looks wrong. Pure black surfaces, elevation that disappears, brand colours that vibrate against dark, a white flash on load, or a mode toggle that does not persist.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.