wp-plugin-security
Skill41 starsChanged 2 months agoGPL-3.0View on GitHub
Security guidelines for WordPress plugin development: sanitization, validation, escaping (PHP and admin JavaScript), nonces, capabilities over objects, multisite boundaries, SQL injection, XSS, CSRF, request headers and the client IP behind proxies, authentication shortcuts, registered meta in REST, and secrets stored in the database. Bundles a release security gate: a procedure and three scripts to run before every release. Use it whenever you write or review plugin code that handles user input, prints dynamic output, registers AJAX or REST endpoints or meta, checks permissions, reads request headers or IP addresses, touches login or two-factor flows, writes files shared by a network, stores copies of configuration, or suppresses PHPCS security sniffs, and whenever a release, a security audit or a reply to the wordpress.org security review is being prepared, even if nobody says the word security. Based on official WordPress Developer Resources and on post-incident reviews of CVE-2026-81754.
- Reads credentials
In this repository4 other files it gives its agents.
- humanizar-texto-esSkill
- humanize-text-enSkill
- wp-plugin-developmentSkill
- wp-plugin-performanceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
30 rules. About 0 are common, 19 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.