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/elvismdev/claude-wordpress-skills/wp-perfgit clone --depth 1 https://github.com/elvismdev/claude-wordpress-skillsWrote 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/commands/elvismdev/claude-wordpress-skills/wp-perf)<a href="https://agentmods.dev/commands/elvismdev/claude-wordpress-skills/wp-perf"><img src="https://agentmods.dev/badge/commands/elvismdev/claude-wordpress-skills/wp-perf.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.00013 | $0.00116 |
| Opus 5 | $0.00006 | $0.00058 |
| Sonnet 5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
wp-perf 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 5d 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.
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.
What it actually says
Use the wp-performance-review skill to perform a quick triage scan.
Target: $ARGUMENTS (if empty, use current working directory)
Focus only on the "Search Patterns for Quick Detection" section—run the grep commands to find critical issues fast. Report matches with file:line references and severity levels. Skip deep analysis.
If critical issues are found, suggest running /wp-perf-review for comprehensive analysis with fixes.
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.
- 5d ago First seen · 12 lines · 13 tokens per session scan A 6cc0947f472d
wp-perf is a command published in the GitHub repository elvismdev/claude-wordpress-skills (227 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 116 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-30.
Other commands, from other repositories
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.
scan
Scan AWS account for cost optimization.