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/convert-to-wp-theme)<a href="https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/convert-to-wp-theme"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/convert-to-wp-theme.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.00023 | $0.01272 |
| Opus 5 | $0.00012 | $0.00636 |
| Sonnet 5 | $0.00005 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
convert-to-wp-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 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/convert-to-wp-theme
Purpose: Convert a complete HTML/CSS/JavaScript project into a production-ready WordPress Block Theme.
Trigger
User types /convert-to-wp-theme followed by project context, OR pastes/attaches HTML files.
Workflow
Step 1: Acknowledge & Gather Context
Respond with a short acknowledgment, then check if these inputs are present in the conversation:
| Required Input | Default if Missing |
|---|---|
| Theme name | Ask once |
| Theme slug | Derive from theme name (lowercase, hyphenated) |
| Author name | Ask once OR use "Theme Author" |
| Source HTML files | Required — must ask if not provided |
| WooCommerce support | Default: NO unless eCommerce keywords detected |
| Build system | Default: Vite 6 with HMR |
| Design tokens | Extract from source CSS (don't ask) |
If any required input is missing, ask the user directly in your response with at most 3 clearly numbered questions in one batch. For optional inputs, use sensible defaults from references/defaults.md and note them in "Decisions Made".
Step 2: Produce Conversion Plan
Before generating any code, produce a markdown table mapping source files to WordPress targets:
## Conversion Plan
| Source File | Target | Type | Notes |
|-------------|--------|------|-------|
| index.html | templates/front-page.html | Template | Hero + features + CTA |
| about.html | templates/page-about.html | Custom Template | Registered in theme.json |
| Header section | parts/header.html | Template Part | |
| Footer section | parts/footer.html | Template Part | |
| Hero section | patterns/hero.php | Pattern | Reused on multiple pages |
| Features grid | patterns/features.php | Pattern | |
| Testimonials | patterns/testimonials.php | Pattern | |
Show this plan. Then say: "Ready to generate the theme. Reply 'go' to proceed, or tell me what to adjust."
Skip the confirmation if the user originally said "just build it" or similar.
Step 3: Execute 10-Phase Methodology
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 · 167 lines · 23 tokens per session scan A 9d7bd31e7cd4
convert-to-wp-theme is a command published in the GitHub repository siddik-web/wp-block-theme-converter (45 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 1,272 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.
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…