Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/siddik-web/wp-block-theme-converternpx agentmods add commands/siddik-web/wp-block-theme-converter/wp-debugWrote 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/siddik-web/wp-block-theme-converter/wp-debug)<a href="https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/wp-debug"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-debug/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/siddik-web/wp-block-theme-converter/wp-debug"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-debug.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.00029 | $0.07891 |
| Opus 5.5 | $0.00012 | $0.03156 |
| Sonnet 5.5 | $0.00006 | $0.01578 |
| Haiku 4.5 | $0.00003 | $0.00789 |
Grade A, and why
wp-debug 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 1mo 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 — 974 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wp-debug
Purpose: Run a guided diagnostic workflow to identify and fix the root cause of a WordPress block theme problem. This command maps symptoms to specific root causes, provides step-by-step diagnosis, and offers to apply fixes directly to theme files.
When to Use
Trigger this command when:
- A block theme is producing an error message in the editor or on the front end
- Styles, colors, typography, or spacing are not applying correctly
- A pattern or template is missing from the Site Editor or inserter
- A file change had no visible effect
- The editor and front end look different
- Shortcodes, widget HTML, or ACF field values are not rendering in blocks
- PHP warnings or notices appear on the front end
When This Command Does NOT Apply
| Situation | Use Instead |
|---|---|
| Converting static HTML/CSS to a block theme | /convert-to-wp-theme |
| Plugin conflict causing a white screen or admin error | /wp-plugin-theme |
| Hosting, server config, or database connection errors | Out of scope — contact hosting provider |
| WP-CLI or SSH access denied | Out of scope — contact server admin |
| Performance / Core Web Vitals issues | Out of scope — use references/asset-optimization.md |
Workflow
Step 1: Gather the Symptom
Ask the user:
"Describe what you're seeing — paste the exact error message if there is one, or describe the behavior (e.g., 'blank page after I edited a block', 'my color palette shows gray instead of my brand colors', 'the hero pattern isn't showing in the inserter')."
If the user already included a symptom in their message with /wp-debug, skip asking and proceed directly to Step 2.
Accept any of these symptom forms:
- Pasted error message (verbatim text from browser or editor)
- Screenshot description ("I see a yellow warning banner in the editor")
- Behavioral description ("nothing changed after I updated the .html file")
- PHP log excerpt
Step 2: Map to Root-Cause Category
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.
- 1mo ago First seen · 974 lines · 29 tokens per session scan A cc20664e364a
wp-debug is a command published in the GitHub repository siddik-web/wp-block-theme-converter (48 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 7,891 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-30.
Other commands, from other repositories
wp-perf-review
WordPress performance code review - detects database anti-patterns, caching issues, hook problems, and scalability concerns.
wp-perf
Quick WordPress performance scan - fast triage using critical pattern detection.
tail-events
Show the latest N ingested events with timestamp, eventtype, and toolname.
health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage.
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
tidy
The structural baseline is empty. scripts/code-quality-baseline.json has no entries, so every gate is live: a new violation is now a hard failure with nothing to hide behind. That is the regime this session works in.