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.
git clone --depth 1 https://github.com/yojahny55/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-settings)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-settings"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-settings.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.00013 | $0.00883 |
| Opus 5 | $0.00006 | $0.00441 |
| Sonnet 5 | $0.00003 | $0.00177 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
wp-settings 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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP Settings — Extend Theme Settings Page
Add new fields, tabs, or sections to the theme's ACF/SCF settings page.
Step 1: Read Project Context
Read .claude/CLAUDE.md to extract:
- Function prefix (e.g.,
kairo_) - Languages (primary + secondary)
- Theme directory path
If .claude/CLAUDE.md does not exist, tell the user to run /wp-init first.
Step 2: Read Existing Settings
Read fields/settings.php in the theme directory to understand:
- Existing tabs and their fields
- Field naming patterns used
- Location rules
- Current structure and organization
If the file does not exist, inform the user that the starter theme's default settings file is missing and offer to create one from scratch.
Step 3: Get Requirements
If $ARGUMENTS is provided, use it as the description of what settings to add.
If $ARGUMENTS is empty, ask the user:
- What settings do they need to add?
- Should these go in a new tab or extend an existing tab?
- Examples: analytics codes, additional contact fields, social platforms, custom scripts, maintenance mode toggle, color overrides
Step 4: Dispatch wp-acf Agent
Dispatch the wp-acf agent with these instructions:
Update
fields/settings.phpin the theme directory to add the following settings:Requirements from user: <paste user requirements or $ARGUMENTS>
Rules:
- DO NOT remove or modify existing fields — only ADD new ones
- If adding a new logical group, create a new Tab field to organize it
- For ALL text, textarea, and wysiwyg fields, create bilingual variants:
<field_name>_en(English variant)<field_name>_es(Spanish variant)- (adjust languages to match project config)
- Follow the existing field naming convention in the file
- Use appropriate field types: text, textarea, wysiwyg, image, url, true_false, select, repeater, etc.
- Add helpful instructions/descriptions to fields so the client understands what each one does
- All fields should have
field_prefixed keys- Ensure the field group location rule keeps pointing to the options page
- After editing the file, invalidate the group's Local JSON so the change re-bootstraps (the loader skips PHP for groups that already have JSON): delete
acf-json/group_settings.jsonand, if the site imported it, run$WP eval "acf_delete_field_group('group_settings');". The next WP load regeneratesacf-json/group_settings.jsonfrom the edited PHP. This discards any manual dashboard edits to the settings group — intended for a code-driven change.Existing settings.php content:
<paste current file content>
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.
- 7d ago First seen · 95 lines · 13 tokens per session scan A 8892474ae098
wp-settings is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 883 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
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
debug-helper
Use when something is broken and you need it diagnosed. A build failure, a runtime crash, a blank page, an unreadable error message, or behaviour that is simply wrong. Gives one exact fix, not a list of things to try.