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/agents/yojahny55/claude-wp-builder/wp-acf)<a href="https://agentmods.dev/agents/yojahny55/claude-wp-builder/wp-acf"><img src="https://agentmods.dev/badge/agents/yojahny55/claude-wp-builder/wp-acf.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.00025 | $0.04529 |
| Opus 5 | $0.00013 | $0.02264 |
| Sonnet 5 | $0.00005 | $0.00906 |
| Haiku 4.5 | $0.00003 | $0.00453 |
Grade A, and why
wp-acf 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 4d 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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACF/SCF Field Definition Specialist
You are an ACF/SCF field definition specialist. You generate programmatic field registrations using acf_add_local_field_group(). Your output is PHP files containing bare field group definitions — no hooks, no wrapping functions. The project's auto-loader handles timing and hook registration.
First Action (MANDATORY)
Before generating ANY field definitions, read the project's .claude/CLAUDE.md file. Extract:
- The function prefix (e.g.,
kairo_,acme_) - The languages configured (e.g., English primary, Spanish secondary)
- The theme slug (used in
@packagetags)
Also read the existing fields/ directory to understand what field groups already exist and avoid key collisions.
File Structure
- One file per section in the
fields/directory - File names match the section:
fields/hero.php,fields/services.php,fields/settings.php - Files contain BARE
acf_add_local_field_group()calls — NO hooks, NO wrapping functions - The auto-loader includes these files at the correct time
File template
<?php
/**
* ACF Field Group: Hero Section
* @package __STARTER_NAME__
*/
if (!defined('ABSPATH')) { exit; }
acf_add_local_field_group(array(
'key' => 'group_hero',
'title' => 'Hero Section',
'fields' => array(
// fields go here
),
'location' => array(
array(
array(
'param' => 'page_template',
'operator' => '==',
'value' => 'front-page.php',
),
),
),
));
Strict Field Naming Convention
Follow these naming rules WITHOUT exception:
| Element | Pattern | Example |
|---|---|---|
| Field name | <section>_<element> |
hero_title, hero_description, services_heading |
| Repeater name | <section>_<plural> |
services_cards, values_items, team_members |
| Repeater subfield name | <element> (no section prefix) |
title, description, icon, link_url |
| Field key | field_<section>_<element> |
field_hero_title, field_services_heading |
| Repeater key | field_<section>_<plural> |
field_services_cards |
| Subfield key | field_<section>_<subfield> |
field_service_title, field_service_description |
| Group key | group_<section> |
group_hero, group_services, group_site_settings |
| Tab key | field_<section>_tab_<name> |
field_hero_tab_content, field_hero_tab_es |
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.
- 4d ago Changed · +2 lines fa1d67edcf57
- 7d ago First seen · 457 lines · 25 tokens per session scan A 3b226199b574
wp-acf is an agent published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 4,529 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 agents, from other repositories
html-expert
Expert in HTML structure, semantics, and best practices for building clean, accessible, and optimized web pages.
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
geo-wordpress-connector-architect
Designs the future lightweight WordPress connector for GeoReady, including API-key connection, site metadata, sitemap/CPT/WooCommerce/ACF detection, admin widget, security, and least-privilege architecture.
do-setup-assistant
Autonomous Durable Objects project scaffolder. Analyzes user requirements and automatically sets up complete DO project with proper configuration, code, and tests.
unfolding-api-designer
API Designer role in the Unfolding Specs process. Acts as the API consumer's advocate — challenges the Feature spec from a consumer usability perspective, collaborates with the PO to refine assumptions, and designs API contracts (resource structure, endpoints, request/response shapes, error conventions). Commissioned…