wp-plugin-theme

wp-plugin-theme is a command for coding agents from siddik-web/wp-block-theme-converter. It costs 16 tokens per session (5,073 once invoked), scanned A, original, MIT.

A WordPress theme helper for declaring which plugins a block theme needs and preparing compatibility code and CSS for them. It covers plugins such as SEO tools, contact forms, custom fields, and online shops.

In plain words
What is it for?
Use it when building a block theme that works with plugins such as Yoast SEO, WPForms, ACF, or WooCommerce, including forms, breadcrumbs, custom fields, and shop features.
Why use it?
It helps prevent plugin features from breaking or looking wrong when used with the theme. It also makes required and optional plugins clear.

Command

Part of the wp-block-theme-converter plugin — 1 skill, 11 commands, 1 agent, 1 hook shipped together

Install

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.

agentmods
npx agentmods add commands/siddik-web/wp-block-theme-converter/wp-plugin-theme
Clone the repo
git clone --depth 1 https://github.com/siddik-web/wp-block-theme-converter

Or install wp-block-theme-converter, the plugin that ships this one along with the rest of its 1 skill, 11 commands, 1 agent, 1 hook.

Wrote 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.

agentmods badge for wp-plugin-theme

README.md
[![agentmods](https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-plugin-theme.svg)](https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/wp-plugin-theme)
Your own site
<a href="https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/wp-plugin-theme"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-plugin-theme.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,073 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.05073
Opus 5 $0.00008 $0.02537
Sonnet 5 $0.00003 $0.01015
Haiku 4.5 $0.00002 $0.00507

Measured 4d ago against content hash 53c2ed9d9af1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wp-plugin-theme 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.

commands/wp-plugin-theme.md · 614 lines

How it starts

The opening of the file, as written. The whole thing — 614 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/wp-plugin-theme

Purpose: Extend a block theme to declare plugin dependencies, add plugin-specific CSS stubs, and generate compatibility code for the most common WordPress plugins (Yoast SEO, WPForms, Gravity Forms, ACF, Jetpack, WooCommerce, and others).

Trigger

User types /wp-plugin-theme OR asks for plugin compatibility in their theme, OR their conversion source HTML references plugin output (e.g., a contact form, SEO breadcrumbs, a review widget).

Workflow

Step 1: Identify Plugins

Ask (or infer from source HTML / context):

Question Why it matters
Which plugins are required (theme breaks without them)? Go into required_plugins declaration
Which plugins are recommended (optional features)? Go into recommended_plugins declaration
Which plugins is the user already using? Determines which CSS stubs to generate
Any page builder plugins (Elementor, Divi)? Different compatibility approach

Common plugins to ask about:

  • Yoast SEO / Rank Math / SEOPress (breadcrumbs, OG tags)
  • WPForms / Gravity Forms / Contact Form 7 (forms)
  • ACF / CMB2 / Meta Box (custom fields)
  • WooCommerce (eCommerce — use /convert-to-wp-theme + references/woocommerce.md instead for full WooCommerce themes)
  • Jetpack (social sharing, related posts)
  • WP Rocket / LiteSpeed Cache (caching plugins)
  • Yoast Duplicate Post / WP All Import (content tools)
  • TranslatePress / Polylang / WPML (translation)
  • The Events Calendar (events)
  • MemberPress / Restrict Content Pro (membership)

Step 2: Produce a Plugin Compatibility Plan

PLUGIN COMPATIBILITY PLAN
==========================
| Plugin              | Status      | What theme generates                              |
|---------------------|-------------|--------------------------------------------------|
| Yoast SEO           | Required    | Breadcrumb template part, OG image size, CSS stub |
| WPForms             | Required    | Form CSS stub, accessibility overrides            |
| ACF                 | Required    | Block Bindings source, post meta registration     |
| Gravity Forms       | Recommended | CSS stub, AJAX compat note                        |
| Jetpack             | Recommended | CSS stub for sharing buttons                      |

Read the full file on GitHub · 614 lines

Changes

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.

  1. 4d ago First seen · 614 lines · 16 tokens per session scan A 53c2ed9d9af1

Subscribe to this mod's changes

wp-plugin-theme is a command published in the GitHub repository siddik-web/wp-block-theme-converter (44 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 5,073 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-30.