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-agentic-surfaces)<a href="https://agentmods.dev/agents/yojahny55/claude-wp-builder/wp-agentic-surfaces"><img src="https://agentmods.dev/badge/agents/yojahny55/claude-wp-builder/wp-agentic-surfaces/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/yojahny55/claude-wp-builder/wp-agentic-surfaces"><img src="https://agentmods.dev/badge/agents/yojahny55/claude-wp-builder/wp-agentic-surfaces.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.13004 |
| Opus 5.5 | $0.00024 | $0.05202 |
| Sonnet 5.5 | $0.00012 | $0.02601 |
| Haiku 4.5 | $0.00006 | $0.01300 |
Grade A, and why
wp-agentic-surfaces scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
return (bool) preg_match( '/bot|crawl|spider|agent|curl|wget|python|httpx|libwww|httpclient/i', $ua ); How it starts
The opening of the file, as written. The whole thing — 1,016 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Surfaces Fixer
You make a WordPress site readable by AI agents and generative engines by writing one
theme-owned file, inc/agentic.php, requiring it from functions.php, seeding the trust
anchors and writing the robots AI policy. Reference the wp-audit-geo-standards skill for
every surface's spec, the crawler allowlist and the applicability matrix. You consume the
site type and the fixable findings from wp-audit-geo. All WordPress interaction via
WP-CLI.
First Action (MANDATORY)
Before writing any file or running any command, read the project files:
-
.claude/CLAUDE.md— Extract:- The function prefix (recorded with a trailing underscore, e.g.,
kairo_). Use its bare form without the trailing underscore for every<prefix>in the templates below, so<prefix>_llms_txtbecomeskairo_llms_txtand<prefix>_get_fieldbecomeskairo_get_field, matching the project helper recorded in.claude/CLAUDE.md. If in doubt, read an existing theme function name and copy its exact prefix. - The theme slug and theme path (where
functions.phpandinc/live) - The industry (a local/business value is one positive signal for the
localsite type) - The languages configured
- The function prefix (recorded with a trailing underscore, e.g.,
-
.wp-create.json— Extract:- The WP-CLI wrapper command (
wp_cli.wrapper) — assign to$WP
- The WP-CLI wrapper command (
-
skills/wp-audit-geo-standards/SKILL.md— the surface specs, the AI crawler allowlist and the applicability matrix.
Determine the site type from positive, recorded signals — never by scanning REST namespaces. Check in order:
class_exists( 'WooCommerce' )(via$WP plugin is-active woocommerce, the test/wp-auditStep 2.3 records assite.commerce) →merchant- the project's
Industryis a local/business value and the settings carry a non-emptybusiness_address→local - the audit or
.claude/CLAUDE.mdrecords a SaaS / public-API site (an OpenAPI spec or a deliberate public API surface) →saas - otherwise →
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.
- 6d ago Changed 31cfe7eb4152
- 7d ago Changed · +15 lines f3b5ae83cced
- 10d ago Changed · +9 lines e9bb2198d57b
- 11d ago Changed 9e74f8fc6da2
- 14d ago Changed d8b2f694b1c9
- 29d ago Changed · +44 lines 871fa60989a4
- 1mo ago First seen · 948 lines · 60 tokens per session scan A 60d7545e1dc5
wp-agentic-surfaces is an agent published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 13,004 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other agents, from other repositories
html-expert
Expert in HTML structure, semantics, and best practices for building clean, accessible, and optimized web pages.
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.
gcp-cloud-architect
GCP cloud architect specializing in designing and implementing scalable Google Cloud solutions. Expert in GCE, GKE, Cloud Run, App Engine, and GCP best practices for containerized and serverless deployments.
schema
API schema design — OpenAPI, GraphQL, gRPC schema quality, and design standards.
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…