Imported from adityaarsharma/wordpress-malware-removal (
SKILL.md). Install upstream withnpx skills add adityaarsharma/wordpress-malware-removal. Copyright stays with the author (AGPL-3.0-or-later).
WordPress Malware Removal — suite router
This repository ships three self-contained skills on one shared, gateway-agnostic engine. This root
file is just the router — the real skills live in skills/ and are installed with ./install.sh.
| Skill | Use it when | Where |
|---|---|---|
| wp-security-audit | "How hackable is this site?" — read-only A–F posture score + ranked fixes. Touches nothing. | skills/wp-security-audit/SKILL.md |
| wp-malware-removal | "This site is hacked — clean it." 12-layer forensic scan → verify → quarantine-first removal → prove clean. | skills/wp-malware-removal/SKILL.md |
| wp-hardening | "Lock the doors." Idempotent, reversible hardening — auto-applies safe fixes, asks before risky. | skills/wp-hardening/SKILL.md |
How to use
- Install:
./install.shcopies all three skills (self-contained:SKILL.md+scripts/+references/) into your agent's skills directory (default~/.claude/skills;--dirfor Codex/Cursor/other;--skill <name>for one;--uninstallto remove). - Connect a gateway: SproutOS MCP (recommended), any other WordPress MCP, or plain SSH+WP-CLI. The
shared contract is
references/gateway.md. - Route by need: unsure? Run wp-security-audit first — it tells you whether to Remove, Harden, or relax.
Shared safety DNA (all three skills)
Read before you act · never irreversible without a restore point · backup is the user's and is enforced, never self-served · quarantine before delete · health-check after every destructive step, auto-rollback on regression · unsure → NEEDS_HUMAN, never auto-delete · honest coverage gaps over silent "all clear."
See README.md for the full guide, SPEC.md for the product/security spec, ROADMAP.md for status,
and docs/research-2026-07-wp-security.md for the sourced research behind the detection/hardening/audit
methodology.