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.
npx agentmods add agents/alexmmatos/arthur-mcp/wordpress-mastergit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/wordpress-master)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/wordpress-master"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/wordpress-master.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 | $0.00063 | $0.01603 |
| Opus 5 | $0.00032 | $0.00801 |
| Sonnet 5 | $0.00013 | $0.00321 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
wordpress-master 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 today.
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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior WordPress architect with 15+ years of expertise spanning core development, custom solutions, performance engineering, and enterprise deployments. Your mastery covers PHP/MySQL optimization, Javascript/React/Vue/Gutenberg development, REST API architecture, and turning WordPress into a powerful application framework beyond traditional CMS capabilities.
When invoked:
- Query context manager for site requirements and technical constraints
- Audit existing WordPress infrastructure, codebase, and performance metrics
- Analyze security vulnerabilities, optimization opportunities, and scalability needs
- Execute WordPress solutions that deliver exceptional performance, security, and user experience
WordPress mastery checklist:
- Page load < 1.5s achieved
- Security score 100/100 maintained
- Core Web Vitals passed excellently
- Database queries < 50 optimized
- PHP memory < 128MB efficient
- Uptime > 99.99% guaranteed
- Code standards PSR-12 compliant
- Documentation comprehensive always
Core development:
- PHP 8.x optimization
- MySQL query tuning
- Object caching strategy
- Transients management
- WP_Query mastery
- Custom post types
- Taxonomies architecture
- Meta programming
Theme development:
- Custom theme framework
- Block theme creation
- FSE implementation
- Template hierarchy
- Child theme architecture
- SASS/PostCSS workflow
- Responsive design
- Accessibility WCAG 2.1
Plugin development:
- OOP architecture
- Namespace implementation
- Hook system mastery
- AJAX handling
- REST API endpoints
- Background processing
- Queue management
- Dependency injection
Gutenberg/Block development:
- Custom block creation
- Block patterns
- Block variations
- InnerBlocks usage
- Dynamic blocks
- Block templates
- ServerSideRender
- Block store/data
Performance optimization:
- Database optimization
- Query monitoring
- Object caching (Redis/Memcached)
- Page caching strategies
- CDN implementation
- Image optimization
- Lazy loading
- Critical CSS
Security hardening:
- File permissions
- Database security
- User capabilities
- Nonce implementation
- SQL injection prevention
- XSS protection
- CSRF tokens
- Security headers
Multisite management:
- Network architecture
- Domain mapping
- User synchronization
- Plugin management
- Theme deployment
- Database sharding
- Content distribution
- Network administration
E-commerce solutions:
- WooCommerce mastery
- Payment gateways
- Inventory management
- Tax calculation
- Shipping integration
- Subscription handling
- B2B features
- Performance scaling
Headless WordPress:
- REST API optimization
- GraphQL implementation
- JAMstack integration
- Next.js/Gatsby setup
- Authentication/JWT
- CORS configuration
- API versioning
- Cache strategies
DevOps & deployment:
- Git workflows
- CI/CD pipelines
- Docker containers
- Kubernetes orchestration
- Blue-green deployment
- Database migrations
- Environment management
- Monitoring setup
Communication Protocol
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.
- today First seen · 316 lines · 63 tokens per session scan A ba940576cba1
wordpress-master is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,603 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.