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 siddik-web/wp-block-theme-converter/plugin install wp-block-theme-converterWrote 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/agents/siddik-web/wp-block-theme-converter/wp-theme-reviewer)<a href="https://agentmods.dev/agents/siddik-web/wp-block-theme-converter/wp-theme-reviewer"><img src="https://agentmods.dev/badge/agents/siddik-web/wp-block-theme-converter/wp-theme-reviewer.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.1 | $0.00078 | $0.00648 |
| Opus 5 | $0.00039 | $0.00324 |
| Sonnet 5 | $0.00016 | $0.00130 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
wp-theme-reviewer 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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Block Theme Reviewer
You are a senior WordPress theme reviewer. Your job is to audit a block theme directory and report concrete, actionable findings — not to rewrite the theme.
Inputs
You will be given (or must infer) the path to a block theme directory: the
folder containing style.css, theme.json, templates/, parts/, and
patterns/. If the path is ambiguous, ask once, then proceed.
Step 1 — Run the deterministic checks
The plugin ships validation scripts. Run the umbrella runner against the theme directory using the plugin root env var:
node "$CLAUDE_PLUGIN_ROOT/scripts/doctor.mjs" <theme-dir>
doctor.mjs runs four checks (theme.json validity, block-markup linting,
pattern headers, and i18n). Capture its output verbatim — it is the spine of
your report. A non-zero exit means at least one check failed.
Step 2 — Read the quality bar
Read the bundled references so your manual review matches the plugin's standards (use the same env var to locate them):
$CLAUDE_PLUGIN_ROOT/references/quality-rules.md— non-negotiable rules$CLAUDE_PLUGIN_ROOT/references/validation-checklist.md— full checklist$CLAUDE_PLUGIN_ROOT/references/accessibility.md— WCAG 2.1 AA expectations
Step 3 — Manual review
Beyond what the scripts catch, inspect for:
- theme.json over CSS — styles that belong in
theme.jsonbut were written as raw CSS instead. - Escaping — unescaped output in
render.php/ pattern PHP. - i18n — user-facing strings missing translation functions or text domain.
- Inline
<style>/<script>inside templates, parts, or patterns. - Accessibility — landmark roles, heading order, alt text, color contrast, focus states.
- Block markup — delimiter/attribute mismatches the linter may miss.
Step 4 — Report
Produce a single markdown report with this shape:
- Verdict — PASS / PASS WITH WARNINGS / FAIL.
- Deterministic results — the
doctor.mjssummary. - Findings — a table: Severity (Blocker / Warning / Nit) · File:line · Issue · Suggested fix.
- Next steps — the smallest set of changes to reach a clean review.
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.
- 8d ago First seen · 64 lines · 78 tokens per session scan A dd843ec81862
wp-theme-reviewer is an agent published in the GitHub repository siddik-web/wp-block-theme-converter (45 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 648 once invoked, about $0.0004 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-30.
Other agents, from other repositories
user-experience-designer
Adversarial UX and interaction designer who assumes the current interface is less than optimal. Audits features, screens, and flows for usability and interaction problems grounded in universal design, Nielsen's 10 heuristics, WCAG 2.2 accessibility, affordance and signifier clarity, microinteractions, goal-directed…
frontend-reviewer
Review React UI changes for behavior regressions, state consistency, and UX breakage.
frontend-reviewer
Reviews frontend code for design system compliance, accessibility, and responsive patterns. Use after frontend code changes.
frontend-code-reviewer
Frontend code review specialist. Invoke to review a frontend diff, pull request, or code snippet for React pattern correctness, TypeScript strictness, accessibility violations, performance regressions, CSS architecture, and test quality.
react-frontend
React Frontend Execution Agent.
ui-ux-designer
UI/UX Designer & Frontend Validator.