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.
git clone --depth 1 https://github.com/yojahny55/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-responsive-check)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-responsive-check"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-responsive-check/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-responsive-check"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-responsive-check.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.00014 | $0.00384 |
| Opus 5.5 | $0.00006 | $0.00154 |
| Sonnet 5.5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
wp-responsive-check 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 18d 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.
What it actually says
WP Responsive Check — Responsive Validation
Responsive validation now lives in /wp-demo-verify. Dispatch to it with the same
argument:
/wp-demo-verify $ARGUMENTS
When the target is an existing site the plugin did not build (a page-builder site, any URL
with no data-motion engine), append --no-motion: the walk then skips the no-engine and
dead-scroll judgments, which would otherwise block every section, and still reports overflow,
clipped copy and the full-page shots. Do not pass it for a page the plugin built.
/wp-demo-verify <url> --no-motion
It walks the five viewports this command used to cover (375, 576, 768, 1024, 1440)
plus 620, 1100, 1152 and 1280, and adds the per-section scroll walk at 1440x900 and 390x844
that a single static screenshot per breakpoint cannot show. The legacy five sample
breakpoint edges only: 1152 sits INSIDE the 1024-1279 band, where lg: utilities
apply with no xl: override yet and a layout can be wrong while both neighbouring
edges look right. 1280 is the first width where xl: applies. 620 samples the band
between 576 and 768, and 1100 the one just under the usual 1140-1200px container. Every
viewport is shot in Firefox too when a Playwright Firefox build exists (see
/wp-demo-verify).
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.
- 18d ago Changed · +9 lines 55aa00f80124
- 1mo ago Changed · +3 lines c15f7e2abb4d
- 1mo ago Changed · +3 lines daf716532922
- 1mo ago Changed · -99 lines cbd597f23f56
- 1mo ago First seen · 118 lines · 14 tokens per session scan A 73b5587ddac3
wp-responsive-check is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 384 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.
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.
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.
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.
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.
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.