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.
npx agentmods add commands/yojahny55/claude-wp-builder/wp-debuggit 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-debug)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-debug"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-debug.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.02671 |
| Opus 5 | $0.00010 | $0.01336 |
| Sonnet 5 | $0.00004 | $0.00534 |
| Haiku 4.5 | $0.00002 | $0.00267 |
Grade A, and why
wp-debug scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| "email", "mail", "smtp" | Test email sending: `bash -c "$WP eval \"var_dump(wp_mail('[email protected]', 'WP Debug Test', 'Testing mail from wp-debug'));\""`. Check if Mailpit is running (Docker): `bash -c "curl -s http How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP Debug — Diagnostics & Debugging
Diagnose WordPress issues by running systematic health checks, identifying problems, and offering targeted WP-CLI fixes. Optionally accepts an issue description to run extra targeted diagnostics.
Step 0: Read Project Context
Read .wp-create.json from the project root to extract the WP-CLI wrapper command.
bash -c "cat .wp-create.json"
Set $WP to the value of wp_cli.wrapper from the manifest (e.g., docker exec my-project-wp wp --allow-root, ddev wp, lando wp, wp --path=/var/www/html/my-project).
If .wp-create.json does not exist:
- Check if bare
wpis available:bash -c "which wp" - If available, set
$WPtowpand continue (assume the current directory is the WordPress root). - If not available, tell the user that WP-CLI is required and stop.
Also determine the environment type for log tailing later:
- If
wp_cli.wrappercontainsdocker exec→ Docker - If
wp_cli.wrapperstarts withddev→ DDEV - If
wp_cli.wrapperstarts withlando→ Lando - Otherwise → Native
Store any user-provided issue description from the command argument for use in Step 2.
Step 1: Always-Run Diagnostics
Run ALL 8 check categories. Execute each command via Bash using bash -c. Collect all output for the report in Step 3.
Check 1: WordPress Health
bash -c "$WP core version"
bash -c "$WP core verify-checksums"
bash -c "$WP eval \"echo PHP_VERSION;\""
bash -c "$WP eval \"echo ini_get('memory_limit');\""
Note the WordPress version, whether checksums pass, PHP version, and memory limit.
Check 2: Debug Configuration
bash -c "$WP config get WP_DEBUG"
bash -c "$WP config get WP_DEBUG_LOG"
bash -c "$WP config get WP_DEBUG_DISPLAY"
Note whether debug mode is enabled, whether logging is active, and whether errors are displayed.
Check 3: Database Health
bash -c "$WP db check"
bash -c "$WP option get siteurl"
bash -c "$WP option get home"
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 First seen · 274 lines · 19 tokens per session scan A 30b23d016228
wp-debug is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 2,671 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.
debug-helper
Use when something is broken and you need it diagnosed. A build failure, a runtime crash, a blank page, an unreadable error message, or behaviour that is simply wrong. Gives one exact fix, not a list of things to try.
status
Check voice-to-claude daemon status and configuration.