wp-security-audit
Skill4 starsChanged 3 days agoMITView on GitHub
WordPress attack-surface security audit of a plugin, theme, or code change. Use when auditing for XSS, SQL injection, CSRF, privilege escalation, REST exposure, secret leaks, or before shipping security-sensitive changes. Produces proven findings with file:line, severity, and fixes - never fabricated. Not for general standards review (use review) or logic correctness proof (use verify).
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- adityaarsharma/wordpress-malware-removaltheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- adityaarsharma/wordpress-malware-removal★ 33same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- diagnosing-bugsSkill
- domain-modelingSkill
- fixSkill
- frontend-designSkill
- grill-meSkill
- grill-with-docsSkill
- gsap-coreSkill
- gsap-performanceSkill
- gsap-pluginsSkill
- gsap-scrolltriggerSkill
- gsap-timelineSkill
- gsap-utilsSkill
- handoffSkill
- landing-page-conversion-auditSkill
- refactorSkill
- researchSkill
- reviewSkill
- share-learningSkill
- tddSkill
- threejs-animationSkill
- threejs-fundamentalsSkill
- threejs-geometrySkill
- threejs-interactionSkill
- threejs-lightingSkill
- threejs-loadersSkill
- threejs-materialsSkill
- threejs-postprocessingSkill
- threejs-shadersSkill
- threejs-texturesSkill
- to-specSkill
- to-ticketsSkill
- verifySkill
- wp-accessibilitySkill
- wp-accessibility-standardsSkill
- wp-css-standardsSkill
- wp-github-actions-standardsSkill
- wp-html-standardsSkill
- wp-i18nSkill
- wp-js-standardsSkill
- wp-performanceSkill
- wp-php-standardsSkill
- wp-pluginSkill
- wp-themeSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Before committing anything that touches input, output, or authorization
- Distinctive: line 15
When a bug report smells like a security issue
- Distinctive: line 16
After any REST endpoint or AJAX handler is written
- Very specific: line 51
Run the canonical 4-step chain — build → format:all:check → phpcs → phpstan, in order, stopping at the first red (see …
≈ “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.
Files
WordPress Security Audit
Delegates to the security-auditor agent. Load docs/wordpress-security.md first — it is
the doctrine; this skill is the procedure.
When to run
- Before committing anything that touches input, output, or authorization
- As a full audit pass before releases
- When a bug report smells like a security issue
- After any REST endpoint or AJAX handler is written
Procedure
- Load
docs/wordpress-security.md - Spawn
security-auditorwith scope: files (diff list or paths) + the threat model (public-facing? admin? logged-in users? what data?) - Triage findings: every finding must be CONFIRMED (data flow traced,
file:linenamed, missing control identified) or explicitly PLAUSIBLE — no vibes - For each confirmed finding, fix with the implementer under the escaping/sanitization matrix — never "fix" by weakening the finding
- Re-run the verification chain after fixes
- Report: findings table, what was fixed, what remains, and any secrets found
Severity guide
| Severity | Example |
| Critical | SQLi with $wpdb interpolation; unauthenticated data exposure |
| High | Stored XSS via unescaped output; CSRF on state change; missing capability on admin AJAX |
| Medium | Escaped-at-store pattern; autoload bloat; missing wp_unslash |
| Low | Nonces without IDs in action strings; debug code left in |
Anti-patterns to check (always)
esc_attr( $url )instead ofesc_url()echo $_GET[...]without sanitize+escape chain$wpdb->query( "SELECT ... $var ..." )is_admin()used as an auth check- REST route with no
permission_callback update_optionon every request instead of autoload:false + transients- API keys hardcoded or in options/i18n strings
Verification chain
Run the canonical 4-step chain — build → format:all:check → phpcs → phpstan, in
order, stopping at the first red (see docs/verification-chain.md).
Secrets additionally: git log -p --all grep for key material, .env* in repo.
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.