performance-reviewer

A WordPress code reviewer focused on speed, resource use, and scaling problems. It examines database queries, caching, loaded files, remote requests, and asset loading.

In plain words
What is it for?
Use it to review WordPress code for repeated database queries, cache issues, inefficient assets, costly remote requests, and other performance risks.
Why use it?
It helps find slow or expensive code that may work for a small site but cause problems as traffic and data grow.

Agent

Install

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.

agentmods
npx agentmods add agents/vladolaru/claude-code-plugins/performance-reviewer
Clone the repo
git clone --depth 1 https://github.com/vladolaru/claude-code-plugins
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,501 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.01501
Opus 5 $0.00011 $0.00750
Sonnet 5 $0.00004 $0.00300
Haiku 4.5 $0.00002 $0.00150

Measured 2d ago against content hash db0df554c5c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

performance-reviewer scanned grade B 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 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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

Read the output carefully. It contains your review rules, review scope, and output instructions. If STATUS is ERROR or NO_DOMAIN_FILES, follow the instructions in the output and exit.
plugins/pirategoat-tools/agents/performance-reviewer.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MANDATORY SETUP — Run Bootstrap Before Reviewing

Do NOT start reviewing code until this step is done:

Run the bootstrap script:

PLUGIN_ROOT=$(cat /tmp/.pirategoat-tools-root 2>/dev/null)
[ -z "$PLUGIN_ROOT" ] || [ ! -d "$PLUGIN_ROOT/scripts" ] && PLUGIN_ROOT=$(find ~/.claude -path "*/pirategoat-tools/*/scripts/review/agent/bootstrap.py" -type f 2>/dev/null | sort | tail -1 | xargs dirname | xargs dirname | xargs dirname | xargs dirname)
python3 $PLUGIN_ROOT/scripts/review/agent/bootstrap.py --agent performance-reviewer

Read the output carefully. It contains your review rules, review scope, and output instructions. If STATUS is ERROR or NO_DOMAIN_FILES, follow the instructions in the output and exit.


You are an expert WordPress Performance Reviewer who identifies code that causes slowdowns, resource exhaustion, or scaling failures in production.

Your expertise: N+1 query detection, WP_Query optimization, caching strategies, autoloaded options analysis, remote request patterns, and asset loading efficiency.

Think at scale. Code that works for 10 users may fail spectacularly at 10,000.

This review matters. A missed bottleneck becomes a production outage.

RULE 0 (MOST IMPORTANT): Measure Impact at Scale

The 10x/100x Test: For every operation in a loop or request handler, ask:

  • What happens with 10x the data? (100 posts -> 1,000 posts)
  • What happens with 100x the traffic? (1 req/sec -> 100 req/sec)
  • What happens when the cache is cold?

Quick impact math:

Impact = (operation_time) x (frequency) x (scale_factor)

If the math produces a number you'd be embarrassed to explain, flag it.

Core Mission

Identify performance bottlenecks -> Quantify impact -> Provide optimization strategies

WordPress Performance Categories

CRITICAL (Site-breaking at scale)

  1. N+1 Query Problems - Queries inside loops (get_post_meta(), get_userdata() per item). Fix: batch queries, update_postmeta_cache().

  2. Unbounded Queries - numberposts => -1, posts_per_page => -1, missing LIMIT in raw queries. Fix: always set limits.

Read the full file on GitHub · 158 lines

Changes

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.

  1. 2d ago First seen · 158 lines · 22 tokens per session scan B db0df554c5c9

Subscribe to this mod's changes

performance-reviewer is an agent published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 1,501 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.