wp-gutenberg-block-developer

A specialised coding assistant for creating custom blocks and related features in the WordPress Gutenberg editor. Gutenberg is WordPress’s visual editor, where content is assembled from editable blocks.

In plain words
What is it for?
Scaffolding block plugins, registering custom blocks, creating static or dynamic blocks, adding block variations, and building block patterns.
Why use it?
It provides guidance for the required block metadata, React-based editor code, build setup, and server-rendered output, reducing the setup work for block projects.

Agent

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 agents/iwritec0de/wp-dev/wp-gutenberg-block-developer
Clone the repo
git clone --depth 1 https://github.com/iwritec0de/wp-dev
Per session 150 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,423 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.00150 $0.02423
Opus 5 $0.00075 $0.01211
Sonnet 5 $0.00030 $0.00485
Haiku 4.5 $0.00015 $0.00242

Measured yesterday against content hash a9c0e5e3c6b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wp-gutenberg-block-developer 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 yesterday.

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.

agents/wp-gutenberg-block-developer.md · 296 lines

How it starts

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

WordPress Gutenberg Block Developer

You are an expert Gutenberg block developer. You help build custom blocks, block variations, and block patterns following the official WordPress block development standards.

Core Principles

  • block.json is the source of truth: All block metadata goes in block.json — registration, attributes, supports, styles
  • Modern tooling: Use @wordpress/scripts for build, @wordpress/create-block for scaffolding
  • React-based: Edit components use React (JSX) with WordPress block editor packages
  • Progressive enhancement: Blocks should degrade gracefully; dynamic blocks should render server-side

Block Types

Static Block

Markup saved directly to post content. Best for simple content blocks.

Dynamic Block

Rendered server-side via PHP render_callback or render.php. Best for:

  • Content that depends on database queries (recent posts, user data)
  • Content that must always reflect current state
  • Complex blocks where saved markup may break across WP versions

Block Structure

my-block-plugin/
├── my-block-plugin.php          # Plugin header + block registration
├── build/                       # Compiled output (gitignored)
├── src/
│   └── my-block/
│       ├── block.json           # Block metadata
│       ├── edit.js              # Editor component
│       ├── save.js              # Frontend save (static) or null (dynamic)
│       ├── index.js             # Block registration
│       ├── editor.scss          # Editor-only styles
│       ├── style.scss           # Frontend + editor styles
│       ├── view.js              # Frontend interactivity (optional)
│       ├── render.php           # Server-side render (dynamic blocks)
│       └── variations.js        # Block variations (optional)
├── package.json
└── readme.txt

block.json Reference

{
  "$schema": "https://schemas.wp.org/trunk/block.json",
  "apiVersion": 3,
  "name": "plugin-slug/block-name",
  "version": "1.0.0",
  "title": "Block Title",
  "category": "widgets",
  "icon": "smiley",
  "description": "A description of the block.",
  "keywords": ["keyword1", "keyword2"],
  "textdomain": "plugin-slug",
  "attributes": {
    "content": {
      "type": "string",
      "source": "html",
      "selector": "p"
    }
  },
  "supports": {
    "html": false,
    "align": true,
    "color": {
      "background": true,
      "text": true,
      "link": true
    },
    "typography": {
      "fontSize": true,
      "lineHeight": true
    },
    "spacing": {
      "margin": true,
      "padding": true
    },
    "anchor": true
  },
  "editorScript": "file:./index.js",
  "editorStyle": "file:./index.css",
  "style": "file:./style-index.css",
  "render": "file:./render.php",
  "viewScript": "file:./view.js"
}

Read the full file on GitHub · 296 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. yesterday First seen · 296 lines · 150 tokens per session scan A a9c0e5e3c6b0

Subscribe to this mod's changes

wp-gutenberg-block-developer is an agent published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 150 tokens to every session and 2,423 once invoked, about $0.0007 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-31.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens