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.
git 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-classic-to-fse)<a href="https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/wp-classic-to-fse"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-classic-to-fse/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-classic-to-fse"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-classic-to-fse.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.00022 | $0.03249 |
| Opus 5 | $0.00011 | $0.01625 |
| Sonnet 5 | $0.00004 | $0.00650 |
| Haiku 4.5 | $0.00002 | $0.00325 |
Grade C, and why
wp-classic-to-fse 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 11d 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:post-featured-image {"isLink":false} /--> How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wp-classic-to-fse
Purpose: Convert an existing classic WordPress theme (PHP template files, functions.php, style.css) into a Full Site Editing (FSE) block theme, preserving the visual design and site structure.
When to Use
This command is specifically for users who already have a WordPress classic theme (one with header.php, footer.php, index.php, single.php, etc.) and want to convert it to a block theme.
- Use this command when the source is an existing WordPress classic theme
- Use
/convert-to-wp-themewhen the source is static HTML/CSS/JS (non-WordPress) - Use
/wp-migratewhen the user wants to migrate content (posts, widgets, ACF) rather than the theme files themselves
Workflow
Step 1: Audit the Classic Theme
Ask the user to provide:
- The theme's
style.css(header metadata) - List of PHP template files present
functions.php(or key sections of it)- Any CSS files and their structure
- Whether any page builders (Elementor, Divi) are being used on top of the classic theme
From these, identify:
CLASSIC THEME AUDIT
====================
Theme name: {{Classic Theme Name}}
Template files: {{list of .php files}}
Style: {{CSS methodology — BEM, utility, custom?}}
Plugins used: {{list active plugins affecting display}}
Dynamic areas: {{sidebars, widget areas, nav menus}}
Custom functionality: {{shortcodes, custom post types, custom queries}}
JavaScript: {{enqueued scripts and their purpose}}
Step 2: Mapping — Classic to FSE
Map each classic theme file to its FSE equivalent:
| Classic File | FSE Equivalent | Notes |
|---|---|---|
header.php |
parts/header.html |
Convert PHP to block markup |
footer.php |
parts/footer.html |
Convert PHP to block markup |
sidebar.php |
parts/sidebar.html |
Widget areas → blocks |
index.php |
templates/index.html |
|
home.php |
templates/home.html |
Blog home page |
front-page.php |
templates/front-page.html |
Static front page |
page.php |
templates/page.html |
|
single.php |
templates/single.html |
|
single-{{cpt}}.php |
templates/single-{{cpt}}.html |
Per CPT |
archive.php |
templates/archive.html |
|
archive-{{cpt}}.php |
templates/archive-{{cpt}}.html |
Per CPT |
category.php |
templates/category.html |
|
tag.php |
templates/tag.html |
|
taxonomy-{{tax}}.php |
templates/taxonomy-{{tax}}.html |
|
search.php |
templates/search.html |
|
404.php |
templates/404.html |
|
comments.php |
Block-based comments in template | core/comments block |
| Custom page template | templates/{{slug}}.html + customTemplates entry in theme.json |
Per template |
woocommerce/ |
WC block templates in templates/ |
See references/woocommerce.md |
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.
- 11d ago First seen · 353 lines · 22 tokens per session scan C 0a05b76cafd1
wp-classic-to-fse is a command published in the GitHub repository siddik-web/wp-block-theme-converter (45 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 3,249 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
tanstack-start
Build a full-stack TanStack Start app on Cloudflare Workers from scratch.
build-website
Build a small site with the simplest stack that fits, fast by default and editable afterwards.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
build-app
Build web client application (Next.js, React, Vite).
ds-check
Audit code against the Designsystemet contracts and the accessibility rules the library cannot enforce. Checks the layer agents actually get wrong — aria-invalid, error-summary placement, export names, invented props, raw hex — by reading each component's contract rather than pattern-matching prose. Reports; never…