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 instructions/bartekmis/wordpress-performance-best-practices/agents-mdgit clone --depth 1 https://github.com/bartekmis/wordpress-performance-best-practicesWhat 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.31497 | $0.31497 |
| Opus 5 | $0.15748 | $0.15748 |
| Sonnet 5 | $0.06299 | $0.06299 |
| Haiku 4.5 | $0.03150 | $0.03150 |
Grade C, and why
wordpress-performance-best-practices AGENTS.md scanned grade C with 2 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- render post --> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(themeAPI.root + 'posts', { How it starts
The opening of the file, as written. The whole thing — 4,059 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Performance Best Practices
Version 1.0.0 WordPress Performance Community January 2026
Note: This document is designed for AI agents and LLMs assisting with WordPress development. It provides structured performance guidelines with clear examples of incorrect and correct implementations.
Abstract
Comprehensive performance optimization guide for WordPress development, designed for AI agents and LLMs assisting developers. This document covers database optimization, caching strategies, asset management, theme development, plugin architecture, media handling, API optimization, and advanced performance patterns. Rules are based on WordPress VIP coding standards, 10up engineering best practices, and official WordPress developer documentation. Each rule includes impact assessment, clear explanations, and practical code examples demonstrating both anti-patterns and recommended implementations.
Table of Contents
1. Database Optimization (CRITICAL)
- 1.1 Avoid post__not_in in WP_Query
- 1.2 Request Only Required Fields
- 1.3 Always Limit Query Results
- 1.4 Optimize Meta Queries with Proper Indexing
- 1.5 Use Prepared Statements for Database Queries
- 1.6 Use WP_Query Instead of Direct Database Queries
2. Caching Strategies (CRITICAL)
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.
- 2d ago First seen · 4,059 lines · 31,497 tokens per session scan C d0ee20e4a9f5
wordpress-performance-best-practices AGENTS.md is an instructions file published in the GitHub repository bartekmis/wordpress-performance-best-practices (12 stars, last pushed 4mo ago), licensed MIT. It adds 31,497 tokens to every session, about $0.1575 per session on Opus 5. A static security scan graded it C with 2 findings (hidden instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.