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-blockgit 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-block)<a href="https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/wp-block"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-block.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.00030 | $0.02730 |
| Opus 5 | $0.00015 | $0.01365 |
| Sonnet 5 | $0.00006 | $0.00546 |
| Haiku 4.5 | $0.00003 | $0.00273 |
Grade A, and why
wp-block 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 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.
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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wp-block
Purpose: Scaffold a custom WordPress block — block.json, edit.js, save.js or render.php, style.css, and editor.css — ready to register inside a block theme.
When to Use
Use this command when no core block (or combination of core blocks in a pattern) satisfies the requirement. Ask before scaffolding a custom block:
"This interaction/layout could also be achieved with a
core/group+ Interactivity API pattern. Do you want a custom block, or would a block pattern be simpler?"
Only proceed with a custom block if the user confirms or the use case clearly requires it (e.g., server-side dynamic rendering with custom REST data, deeply custom editor UI, registering a new block type for a plugin).
Workflow
Step 1: Gather Block Requirements
Ask (or infer from context):
| Question | Default if silent |
|---|---|
| Block name (human-readable) | Required — always ask |
Block slug (namespace/block-name) |
Derive from theme slug + block name |
| Block category | theme |
| Block type: static (save.js renders HTML) or dynamic (render.php renders HTML server-side) | Ask — explain the tradeoff below |
| Attributes needed | Infer from description |
| Supports needed (innerBlocks, align, color, typography, spacing) | Minimal — only what's asked |
| Icon | block-default (dashicons slug) |
| Keywords | 3 inferred from block name |
Static vs Dynamic — explain the tradeoff:
| Static Block | Dynamic Block | |
|---|---|---|
| Output stored in | Post content (HTML) | Database (attributes only) |
| Re-renders when | Post saved | Every page load |
| Best for | Design components (hero, card, CTA) | Data-driven content (recent posts, live inventory) |
save.js |
Required | Must return null |
render.php |
Not used | Required |
Step 2: Plan the Block Structure
State the file list before generating:
BLOCK PLAN: {{namespace}}/{{block-name}}
Type: Static | Dynamic
Files to generate:
blocks/{{block-name}}/block.json
blocks/{{block-name}}/edit.js
blocks/{{block-name}}/save.js (static only)
blocks/{{block-name}}/render.php (dynamic only)
blocks/{{block-name}}/style.css
blocks/{{block-name}}/editor.css
inc/block-registration.php (only if not already present)
Attributes: [list]
Supports: [list]
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 · 333 lines · 30 tokens per session scan A c2cdfd483fa1
wp-block is a command published in the GitHub repository siddik-web/wp-block-theme-converter (45 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 2,730 once invoked, about $0.0002 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
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).