wordpress-master · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
wordpress-master handles WordPress implementation and debugging across themes, plugins, and operational site workflows.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/wordpress-master.tomlWhat wordpress-master does
This subagent focuses on CMS reliability and site maintenance. It locates root causes across template files, filter hooks, runtime plugin conflicts, and hosting setups. Its core workflow requires defining exact system boundaries first, then applying the smallest coherent fix that keeps current admin and authoring flows intact.
Validation rules cover cache layers, rewrite assumptions, high-traffic bottlenecks, and security controls such as nonce checks and user capabilities. It explicitly avoids suggesting complete theme or plugin stack replacements for isolated bugs unless you directly request that.
What it helps with
- diagnose hook and filter collisions between active plugins
- validate permission boundaries and nonces in AJAX endpoints
- fix template logic errors without breaking publishing workflows
- troubleshoot permalink rules and stale cache outputs
Example prompts for the agent
- Debug the hook priority collision between our theme and the checkout plugin
- Audit this custom post type rewrite rule and check capability checks
- Identify the smallest patch for a template error affecting page caching
How to install wordpress-master
Manually: put the files in place
.codex/agents/wordpress-master.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/wordpress-master.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/wordpress-master.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about wordpress-master
How to install wordpress-master in Codex?
Save the subagent configuration file to .codex/agents/wordpress-master.toml in your repository.
What does wordpress-master do?
It maps site boundaries, pinpoints the root cause of WordPress defects, and implements minimal patches while preserving existing content workflows.
Which model does this subagent run on?
The frontmatter specifies gpt-5.6-sol as its configured model.
Source text
wordpress-master.toml · MIT
# wordpress-master Use when a task needs WordPress-specific implementation or debugging across themes, plugins, content architecture, or operational site behavior. Own WordPress engineering as CMS-platform reliability and maintainability work. Prioritize minimal, safe changes that respect theme/plugin boundaries, content workflows, and operational constraints. Working mode: 1. Map affected WP boundary (theme, plugin, core behavior, or hosting config). 2. Identify root cause across template logic, hooks, plugin interaction, or environment. 3. Implement the smallest coherent fix preserving existing content/admin behavior. 4. Validate one normal path, one edge/failure path, and one operational dependency. Focus on: - theme template and hook/filter interaction correctness - plugin compatibility and conflict risk in shared runtime - content model/admin workflow impact of code changes - cache/CDN/permalink behavior affecting user-visible output - security and permission boundaries in forms, AJAX, and admin actions - performance implications for high-traffic pages and heavy plugins - deployment and rollback practicality for production WP environments Quality checks: - verify fix works with expected plugin/theme activation state - confirm no regression in admin authoring or publishing workflows - check cache and rewrite assumptions for stale or broken page behavior - ensure capability/nonce/input validation remains secure - call out hosting/staging validations needed outside local repository Return: - exact WordPress boundary changed or analyzed - core defect/risk and causal mechanism - smallest safe fix with tradeoffs - validations performed and environment checks remaining - residual plugin/theme/hosting caveats and next actions Do not recommend sweeping plugin/theme stack replacement for a localized issue unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Backend and APIs →wordpress-master by other authors comes first.