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/vladolaru/claude-code-plugins/wordpress-backend-devnpx skills add vladolaru/claude-code-plugins --skill wordpress-backend-devgit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWrote 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/skills/vladolaru/claude-code-plugins/wordpress-backend-dev)<a href="https://agentmods.dev/skills/vladolaru/claude-code-plugins/wordpress-backend-dev"><img src="https://agentmods.dev/badge/skills/vladolaru/claude-code-plugins/wordpress-backend-dev.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.00066 | $0.02470 |
| Opus 5 | $0.00033 | $0.01235 |
| Sonnet 5 | $0.00013 | $0.00494 |
| Haiku 4.5 | $0.00007 | $0.00247 |
Grade A, and why
wordpress-backend-dev 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Directory
Resolve SKILL_DIR to the absolute directory containing this SKILL.md, as
shown by the current host, before using any bundled path below.
Before a shell command uses $SKILL_DIR, assign it in that command or replace
it with the resolved path. It is not a host-exported environment variable.
WordPress Backend Development
This skill provides comprehensive guidance for WordPress backend PHP development, covering coding standards, internationalization, security, and best practices.
When to Use This Skill
Use this skill when:
- Writing PHP code for WordPress plugins or themes
- Reviewing WordPress PHP code for quality
- Implementing internationalization (i18n) for translatable strings
- Working with WordPress hooks (actions and filters)
- Handling database operations with WPDB
- Building REST API endpoints
- Implementing AJAX handlers
- Creating admin menu pages and settings screens
- Ensuring security in WordPress code
Common Errors This Skill Addresses
If you encounter these errors, this skill has the fix:
| Error/Symptom | Solution Location |
|---|---|
WordPress.Security.EscapeOutput |
security.md → Output Escaping |
WordPress.Security.NonceVerification |
security.md → Nonces |
WordPress.Security.ValidatedSanitizedInput |
security.md → Input Sanitization |
WordPress.DB.PreparedSQL |
database.md → Prepared Statements |
WordPress.WP.I18n errors |
i18n.md → Core Functions |
Translators comment is malformed |
i18n.md → Translator Comments |
| "Security check failed" | security.md → Nonces |
| "Permission denied" | security.md → Capability Checks |
| XSS vulnerability in code review | security.md → Output Escaping |
| SQL injection warning | database.md → Prepared Statements |
| CSRF vulnerability | security.md → Nonces |
| "Nonce verification failed" | security.md → AJAX Nonces |
rest_forbidden error |
rest-api-authentication.md |
| AJAX returns 0 or -1 | ajax.md → Common Issues |
What ships with it
14 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.
- references/admin-menus.md 15 KB
- references/ajax.md 28 KB
- references/coding-standards.md 8.0 KB
- references/database.md 12 KB
- references/hooks-api.md 12 KB
- references/http-api.md 31 KB
- references/i18n.md 13 KB
- references/rest-api-authentication.md 12 KB
- references/rest-api-controllers.md 21 KB
- references/rest-api-endpoints.md 21 KB
- references/rest-api.md 6.5 KB
- references/security.md 29 KB
- references/transients.md 17 KB
- references/users.md 29 KB
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 · 257 lines · 66 tokens per session scan A ce87148d6642
wordpress-backend-dev is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 2,470 once invoked, about $0.0003 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-09-03.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…