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 commands/iwritec0de/wp-dev/wp-perf-auditgit 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.00013 | $0.00536 |
| Opus 5 | $0.00006 | $0.00268 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
wp-perf-audit 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wp-perf-audit
Run a static performance audit on the current WordPress project.
Usage
/wp-perf-audit [path]
- No argument: scans the entire project
- With path: scans only the specified directory (e.g.,
/wp-perf-audit includes/)
Instructions
Load the wordpress-performance skill for optimization patterns and anti-patterns.
Delegate the audit to the wp-perf-analyzer agent by using the Task tool with the following prompt:
"Perform a comprehensive WordPress performance audit on the current project{path_scope}. Scan all PHP files and check for:
- Unbounded queries —
posts_per_page => -1, missing LIMIT in raw SQL - N+1 query patterns —
get_post_meta()/get_option()inside loops without cache priming - Queries on every request — database calls in
init/plugins_loadedwithout conditional guards - Batch operation gaps — individual
$wpdb->insert()/update()in loops - Missing
no_found_rows—WP_Querywithoutno_found_rows => truewhen no pagination is used - Unnecessary cache priming —
fields => 'ids'queries that still prime meta/term caches - Repeated
get_option()calls — same option fetched in multiple functions - Autoload bloat — large data stored with autoload enabled
- Uncached external HTTP —
wp_remote_get()without transient caching - Heavy init hooks — expensive operations on early-firing hooks
- Leading wildcard LIKE —
LIKE '%term'in SQL queries - Admin asset loading — scripts/styles enqueued on all admin pages
Output a structured report with:
- Severity levels: CRITICAL, WARNING, INFO
- File path and line number for each finding
- Impact description
- Suggested fix with code snippet
- Summary statistics and estimated query reduction
- Prioritized recommendations
Sort findings by severity (CRITICAL first)."
Replace {path_scope} with the user's path argument if provided (e.g., " within the includes/ directory"), or remove it if no argument was given.
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 · 51 lines · 13 tokens per session scan A 8728280adf1c
wp-perf-audit is a command published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 536 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.