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/alessioarzenton/claude-code-wp-toolkit/wp-plugin-developmentnpx skills add alessioarzenton/claude-code-wp-toolkit --skill wp-plugin-developmentgit clone --depth 1 https://github.com/alessioarzenton/claude-code-wp-toolkitWrote 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/alessioarzenton/claude-code-wp-toolkit/wp-plugin-development)<a href="https://agentmods.dev/skills/alessioarzenton/claude-code-wp-toolkit/wp-plugin-development"><img src="https://agentmods.dev/badge/skills/alessioarzenton/claude-code-wp-toolkit/wp-plugin-development.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.00035 | $0.02195 |
| Opus 5 | $0.00017 | $0.01097 |
| Sonnet 5 | $0.00007 | $0.00439 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
wp-plugin-development 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 4d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 282 lines · 35 tokens per session scan A ef155c1f58f9
wp-plugin-development is a skill published in the GitHub repository alessioarzenton/claude-code-wp-toolkit (24 stars, last pushed 6mo ago), licensed GPL-3.0. It adds 35 tokens to every session and 2,195 once invoked, about $0.0002 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 skills, from other repositories
xmlrpc-exploitation
Exploit XMLRPC multicall, pingback for brute force and SSRF.
cms-detection
Identify CMS, frameworks, and server technology stacks on live hosts.
cors-credential-wordpress
Exploit WP CORS credential reflection for data theft.
wordpress-full-compromise
Use when verified WordPress findings may combine into an authorized path to administrative or server control.
wordpress-plugin-hunt
Hunt WP plugins via REST, exploit CVEs when version known.
woocommerce-markdown
Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.