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/siddik-web/wp-block-theme-converter/wp-migrategit clone --depth 1 https://github.com/siddik-web/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/commands/siddik-web/wp-block-theme-converter/wp-migrate)<a href="https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/wp-migrate"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-migrate.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.00029 | $0.04245 |
| Opus 5 | $0.00015 | $0.02122 |
| Sonnet 5 | $0.00006 | $0.00849 |
| Haiku 4.5 | $0.00003 | $0.00424 |
Grade C, and why
wp-migrate scanned grade C 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- wp:paragraph { "metadata": { "bindings": { "content": { "source": "core/post-meta", "args": { "key": "{{meta_key}}" } } } } } --> How it starts
The opening of the file, as written. The whole thing — 488 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wp-migrate
Purpose: Generate the code, queries, and patterns needed to migrate existing WordPress content — classic editor posts, widget areas, ACF fields, shortcodes, or Custom Post Types — into the new block theme structure.
When to Use
Trigger this command when:
- The user has an existing WordPress site (not a static HTML project) they are upgrading to a block theme
- The user wants to convert Classic Editor content to block editor content
- The user has custom fields (ACF, CMB2, Meta Box) they want to surface via Block Bindings API
- The user has widget areas they want to replace with template parts
- The user has shortcodes they want to replace with blocks or patterns
- The user has a Custom Post Type they want to surface via Query Loop or a custom dynamic block
This command is NOT for converting static HTML → WordPress (use /convert-to-wp-theme for that).
Page Builder Detection
If the user mentions or you detect a page builder in scope, load references/page-builder-migration.md before Step 2. That reference contains per-builder playbooks with element→block mapping tables, WP-CLI extraction commands, and worked examples. Use the builder-specific workflow from that reference instead of the generic approach below for content extraction.
| Builder detected | Action |
|---|---|
| Elementor / Elementor Pro | Load page-builder-migration.md §1 |
| Divi / Divi Builder | Load page-builder-migration.md §2 |
| WPBakery / Visual Composer | Load page-builder-migration.md §3 |
| Beaver Builder / BB Themer | Load page-builder-migration.md §4 |
| Classic Gutenberg (no builder) | Load page-builder-migration.md §5 |
| None / unknown | Continue with generic workflow below |
Workflow
Step 1: Identify Migration Scope
Ask (or infer from context):
| Question | Why it matters |
|---|---|
| WordPress version currently running | Determines available migration tools |
| Active page builder (Elementor, Divi, Beaver Builder, WPBakery, none) | Different conversion strategies per builder — see page-builder-migration.md |
| Using Classic Editor or already using Gutenberg? | Classic content needs block conversion |
| Custom Post Types (CPTs) — list their slugs | Need Query Loop templates or custom blocks |
| Custom fields plugin (ACF, CMB2, Meta Box, Pods, none) | Determines Block Bindings approach |
| Widget areas — list names and their content | Become template parts in block theme |
| Shortcodes in use — list them | Need block or pattern equivalents |
| How many posts/pages need migration (estimate) | Batch vs programmatic migration |
| WooCommerce products? | WooCommerce-specific template migration |
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.
- 5d ago First seen · 488 lines · 29 tokens per session scan C d736a081a0b4
wp-migrate is a command published in the GitHub repository siddik-web/wp-block-theme-converter (45 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 4,245 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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-dev-learn
Extract learnings from the current session and update wp-dev-skills skill files — captures corrections, new rules, edge cases, and Common Mistakes entries discovered during real usage. Only globally applicable WP developer standards accepted — project-specific rules are redirected. Use suggest to see WP dev topics not…
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.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
claude-recall
Update project context using the local LLM (Qwen2.5 0.5B).