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 skills/trtmn/agent-plugins/wp-localnpx skills add trtmn/agent-plugins --skill wp-localgit clone --depth 1 https://github.com/trtmn/agent-pluginsWhat 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.00118 | $0.01684 |
| Opus 5 | $0.00059 | $0.00842 |
| Sonnet 5 | $0.00024 | $0.00337 |
| Haiku 4.5 | $0.00012 | $0.00168 |
Grade B, and why
wp-local 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 for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Secrets are in `.env`** — stored at `~/wordpress-sites/<name>/.env` (chmod 600). Do not print this file. How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wp-local — Local WordPress Site Manager
Spin up fully functional local WordPress sites using Docker Compose. Each site gets its own port, isolated MySQL database, and WP-CLI-configured admin account with a forced password change on first login.
Sites persist in ~/wordpress-sites/<name>/ and survive reboots as long as Docker is running.
Scripts
All scripts live at ${CLAUDE_PLUGIN_ROOT}/skills/wp-local/scripts/. They output JSON to stdout; progress and errors go to stderr.
| Script | Purpose |
|---|---|
check-deps.sh |
Verify Docker and Docker Compose are available and the daemon is running |
list.sh |
List all sites in ~/wordpress-sites/ with their running/stopped status |
create.sh <name> [title] |
Create a new site — takes ~1-2 min first run (image pull) |
start.sh <name> |
Start a stopped site |
stop.sh <name> |
Stop a running site (data is preserved) |
destroy.sh <name> <name> |
Permanently destroy a site — second arg must match first (safety guard) |
Workflow
Step 1: Check dependencies
Delegate to the wp-local-ops agent synchronously (NOT in background — the result is needed before proceeding):
Operation: check-deps
Parse the JSON response. If ok is false, display each message from the errors array clearly and stop. Do not proceed until Docker is running and Compose is available.
Step 2: Determine intent
If the user's message already specifies the action (e.g. "create a site called my-demo", "stop my WordPress site", "list my sites", "destroy the test site"), go directly to that action — skip the question.
Otherwise, ask:
AskUserQuestion:
question: "What would you like to do with your local WordPress sites?"
options:
- Create a new site — spin up a fresh WordPress instance with WP-CLI
- List my sites — show all local WordPress sites and their status
- Start a site — bring a stopped site back online
- Stop a site — pause a running site (data is preserved)
- Destroy a site — permanently delete a site and all its data
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 179 lines · 118 tokens per session scan B 449bea54e47e
wp-local is a skill published in the GitHub repository trtmn/agent-plugins (2 stars, last pushed 5d ago), licensed Unlicense. It adds 118 tokens to every session and 1,684 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.