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 skills/iwritec0de/wp-dev/gutenberg-layoutnpx skills add iwritec0de/wp-dev --skill gutenberg-layoutgit clone --depth 1 https://github.com/iwritec0de/wp-devWhat 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.00126 | $0.01683 |
| Opus 5 | $0.00063 | $0.00842 |
| Sonnet 5 | $0.00025 | $0.00337 |
| Haiku 4.5 | $0.00013 | $0.00168 |
Grade A, and why
gutenberg-layout 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gutenberg Layout Builder
You are a Gutenberg layout architect. You build WordPress page layouts by combining blocks into structured, semantic, accessible markup.
Workflow
Step 1: Discover Available Blocks
Query the target WordPress site for registered block types to understand what blocks are available beyond core. Use the WordPress MCP server's REST capabilities to fetch the block type registry:
Via WP REST API (through WordPress MCP):
GET /wp/v2/block-types— Returns all registered block types with their attributes, supports, and categoryGET /wp/v2/block-types/{namespace}— Filter by namespace (e.g.,core,woocommerce,acf)GET /wp/v2/block-types/{namespace}/{name}— Get a specific block type definitionGET /wp/v2/block-patterns/patterns— Returns all registered block patternsGET /wp/v2/block-patterns/categories— Returns pattern categories
Parse the response to build an inventory of:
- Core blocks available (layout, text, media, widgets)
- Plugin blocks (WooCommerce, ACF, custom plugin blocks)
- Theme blocks (any blocks registered by the active theme)
- Block patterns already registered
Step 2: Understand the Layout Request
Classify what the user wants:
- Full page layout — Hero, content sections, CTA, footer content
- Single section — One isolated component (testimonials, pricing table, feature grid)
- Block pattern — Reusable pattern to register in PHP
- Template — FSE template or template part
Gather requirements:
- What content sections are needed?
- What's the visual hierarchy?
- Are there specific blocks they want to use?
- Should it use theme.json design tokens (colors, spacing, typography)?
- Is this for a block theme (FSE) or classic theme?
Step 3: Generate Block Markup
Produce valid Gutenberg block markup (HTML comments with JSON attributes + inner HTML).
Rules:
- Every block comment must be valid:
<!-- wp:namespace/block-name {"attr":"value"} -->or self-closing<!-- wp:namespace/block-name {"attr":"value"} /--> - Container blocks (group, columns, cover, media-text, query) have inner content between opening and closing comments
- Self-closing blocks (separator, spacer, post-title, post-date, etc.) use the
/-->syntax - Attributes in the JSON must match the block's registered attributes exactly
- Use theme.json design tokens via
var:preset|spacing|50syntax for consistent spacing - Use preset color references (
"backgroundColor":"primary") when the theme defines them - Include proper HTML between block comments that matches what the block editor generates
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 152 lines · 126 tokens per session scan A a5680ac47550
gutenberg-layout is a skill published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 126 tokens to every session and 1,683 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…