Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yojahny55/claude-wp-builder/plugin install claude-wp-builderWrote 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/yojahny55/claude-wp-builder/wp-header)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-header"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-header.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.00019 | $0.03803 |
| Opus 5 | $0.00010 | $0.01902 |
| Sonnet 5 | $0.00004 | $0.00761 |
| Haiku 4.5 | $0.00002 | $0.00380 |
Grade A, and why
wp-header 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 3d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP Header — WordPress Header Builder
Generate a fully functional WordPress header with responsive navigation, logo from settings, language switcher, and WP menu system integration.
Step 1: Read Project Context
Read .claude/CLAUDE.md to extract:
- Function prefix (e.g.,
kairo_) - Theme slug
- Languages (primary + secondary)
- Theme directory path
If .claude/CLAUDE.md does not exist, tell the user to run /wp-init first.
Step 2: Read Demo Header
Read demo/index.html and extract the header/nav section (between <!-- ============ SECTION: Header ============ --> delimiters, or the <header> element).
Analyze:
- Navigation structure (single-level or dropdowns)
- Logo placement (left, center, etc.)
- Language switcher position
- Whether the header is sticky/fixed
- CTA button in nav (if any)
- Mobile menu behavior
Step 3: Screenshot Reference (Optional)
If $ARGUMENTS provides a screenshot path, read the screenshot file for additional visual reference. Use it to inform layout decisions that might not be captured in the HTML demo.
Step 4: Dispatch wp-template Agent
Dispatch the wp-template agent with these instructions:
Generate the following files in the theme directory:
header.php
- Start with
<!DOCTYPE html>,<html <?php language_attributes(); ?>>,<head>,<meta charset>,<meta viewport>,<?php wp_head(); ?>,</head><body <?php body_class(); ?>>- Site header with:
- Logo from settings:
prefix_get_field('site_logo', 'option')with fallback toget_bloginfo('name')wp_nav_menu()call using the location the project'si18n strategyregisters: undersuffix, the per-language location ('primary_' . prefix_get_current_lang()); underpolylang, the bare location (primary) — Step 7 registers one location per name there- Use the custom nav walker class
- Language switcher per the project's
i18n strategy: undersuffix, render all configured languages (fromSUPPORTED_LANGS) with active state, linking throughprefix_get_lang_url(); underpolylang, render it withpll_the_languages()— Step 7 says why (it marks the current language and hides languages with no counterpart)- Mobile hamburger toggle button with aria attributes
- Skip-to-content link for accessibility
inc/nav-walker.php
- Custom Walker_Nav_Menu extension named
Prefix_Nav_Walker(using actual prefix)- Support for dropdown/submenu items if the demo has them
- Proper escaping on all output
Class naming — include the line matching the project's
Template:, drop the otherBoth files above are yours on both paths; only the class system changes.
basic→ BEM class naming on output elementstailwind→ keep the Tailwind utility classes already on the demo header you were handed, element for element. Never replace them with BEM names and never invent new class names:wp-tailwindruns after you and renames only the groups its promotion ladder promotes. See "File ownership" under "CSS agent routing" below.Make sure to match the visual layout from the demo as closely as possible.
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.
- 3d ago Changed · +13 lines 8181750011d5
- 6d ago First seen · 307 lines · 19 tokens per session scan A fb80b553efb4
wp-header is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 3,803 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
accessibility-specialist
Use when a screen might fail WCAG. Unlabeled inputs, no keyboard path, contrast below AA, missing landmarks, broken heading order, screen reader gaps, or a request for an a11y review or EU Accessibility Act check.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
conversational-ui-designer
Use when designing a chat or assistant interface. Message layout, bot personality, streaming and typing states, rich message cards, error recovery, or voice input.
form-designer
Use when a form is losing people. Too many fields, validation that interrupts typing, unclear required fields, a multi-step flow with no sense of progress, or inputs with no labels.
healthcare-ux-specialist
Use when designing clinical or patient-facing interfaces. Clinical workflows, displaying sensitive patient data, HIPAA considerations in the UI, and medical terminology patients do not speak.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.