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/iwritec0de/wp-dev/wp-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.00014 | $0.02043 |
| Opus 5 | $0.00007 | $0.01022 |
| Sonnet 5 | $0.00003 | $0.00409 |
| Haiku 4.5 | $0.00001 | $0.00204 |
Grade A, and why
wp-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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wp-gutenberg-layout
Generate Gutenberg page layouts by discovering available blocks on a WordPress site and producing valid block markup.
Skills
Load the gutenberg-layout skill for block discovery, composition, and markup patterns.
Usage
The user provides a layout description after the command. Examples:
/wp-gutenberg-layout landing page for a SaaS product/wp-gutenberg-layout blog archive with featured post and grid/wp-gutenberg-layout pricing page with 3 tiers/wp-gutenberg-layout hero + features + testimonials + CTA
If no arguments are provided, ask the user what layout they need using AskUserQuestion.
Workflow
1. Discover Available Blocks
Check if a WordPress site is connected via the WordPress MCP server. If connected:
- Fetch registered block types via
GET /wp/v2/block-typesto discover all available blocks (core + plugins + theme) - Fetch registered patterns via
GET /wp/v2/block-patterns/patterns - Fetch theme.json settings if available (color palette, spacing scale, typography) to use design tokens
If no WordPress MCP connection is available, fall back to the core blocks reference at skills/gutenberg-layout/references/core-blocks.md.
Present a brief summary to the user:
- Number of core blocks available
- Any notable plugin blocks (WooCommerce, ACF, etc.)
- Relevant existing patterns they could extend
- Theme design tokens (colors, fonts, spacing) available
2. Gather Requirements
Based on the user's description, determine:
- Layout type: Full page, single section, or reusable pattern?
- Sections needed: Hero, features, CTA, testimonials, pricing, FAQ, etc.
- Content specifics: What text, images, links should be included?
- Design preferences: Colors, spacing, alignment preferences?
- Output format: Raw block markup, PHP pattern registration, or HTML template file?
- Block theme or classic?: Affects available blocks and registration approach
Ask clarifying questions with AskUserQuestion only if the request is genuinely ambiguous. For straightforward requests, proceed with sensible defaults.
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 · 186 lines · 14 tokens per session scan A 216eed5e3d1b
wp-gutenberg-layout is a command published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 2,043 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.