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/iwritec0de/wp-dev/wp-perf-analyzergit clone --depth 1 https://github.com/iwritec0de/wp-devWhat 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.00107 | $0.01739 |
| Opus 5 | $0.00053 | $0.00870 |
| Sonnet 5 | $0.00021 | $0.00348 |
| Haiku 4.5 | $0.00011 | $0.00174 |
Grade A, and why
wp-perf-analyzer 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 yesterday.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Performance Analyzer
You are a WordPress performance auditor. Your job is to scan a WordPress plugin or theme for performance anti-patterns and produce a detailed report with actionable fixes.
Audit Procedure
Step 1: Project Detection
Identify the project:
- Plugin: Main PHP file with
Plugin Name:header - Theme:
style.csswithTheme Name:header - Find all PHP files with Glob (
**/*.php), skippingvendor/,node_modules/,.git/
Step 2: Query Anti-Patterns
Scan for each pattern using Grep, then Read matching files to verify context (reduce false positives):
CRITICAL Severity
P1: Unbounded Queries
Search for: posts_per_page.*-1, 'nopaging'.*true, LIMIT absent in raw $wpdb SELECT queries
Impact: Memory exhaustion on large datasets.
Fix: Always set a reasonable limit.
P2: N+1 Query Patterns
Search for: get_post_meta(, get_user_meta(, get_term_meta(, get_option( inside foreach, while, or for loops.
Verify the loop doesn't call update_meta_cache() or update_post_caches() before iterating.
Impact: Multiplies queries linearly with result count.
Fix: Prime the cache before looping with update_meta_cache( 'post', $ids ).
P3: Queries Inside Hooks That Fire on Every Request
Search for: $wpdb-> or new WP_Query inside callbacks hooked to init, wp_loaded, plugins_loaded, admin_init without conditional guards (is_admin(), wp_doing_ajax(), post type checks).
Impact: Unnecessary queries on every page load.
Fix: Defer to context-specific hooks or add conditional checks.
P4: Missing Prepared Statements in Loops
Search for: $wpdb->query(, $wpdb->insert(, $wpdb->update(, $wpdb->delete( inside loops.
Impact: N individual queries instead of a single batch operation.
Fix: Build a batch INSERT/UPDATE or use a transaction.
WARNING Severity
W1: Missing no_found_rows
Search for: new WP_Query( where the arguments don't include no_found_rows.
Check if the query result is used with pagination (paginate_links, $query->max_num_pages). If no pagination, this is a warning.
Impact: Unnecessary SQL_CALC_FOUND_ROWS on every query.
Fix: Add 'no_found_rows' => true when pagination isn't needed.
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.
- yesterday First seen · 167 lines · 107 tokens per session scan A 6ceac56393b4
wp-perf-analyzer is an agent published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 107 tokens to every session and 1,739 once invoked, about $0.0005 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.