More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    WordPress Hardening & Security Audit

    2

    Secure Your WordPress Infrastructure WordPress powers over 40% of the web, making it the primary target for automated mass-exploitation.

    $8.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    WordPress Hardening & Security Audit

    WordPress Hardening & Security Audit

    Example session with this skill installed

    Audit our WordPress 6.6 site on Ubuntu with nginx and PHP-FPM 8.2. xmlrpc.php is reachable, DISALLOW_FILE_EDIT isn't set, wp-config.php is in the webroot with 644 permissions, the main admin user is called "admin", and nobody uses 2FA.

    • Read your context and instructions
    • Compiled the wordpress hardening

    Security audit of the five items you described: 4/10. Two high-severity gaps are fixable in under an hour.

    #AreaFindingSeverityFix
    1AuthNo 2FA on admin accountsHighEnforce 2FA for administrators
    2AuthUsername "admin"HighNew admin user, reassign content, delete "admin"
    3Attack surfacexmlrpc.php reachableMediumBlock in nginx unless Jetpack or the app needs it
    4ConfigDashboard file editor enabledMediumDISALLOW_FILE_EDIT
    5Fileswp-config.php at 644 in webrootMedium640, owner deploy user, group PHP-FPM

    wp-config.php

    define( 'DISALLOW_FILE_EDIT', true );
    define( 'FORCE_SSL_ADMIN', true );
    

    nginx server block

    location = /xmlrpc.php { deny all; return 403; }
    location = /wp-config.php { deny all; }
    location ~* /wp-content/uploads/.*\.php$ { deny all; }
    

    Permissions

    chown deploy:www-data wp-config.php
    chmod 640 wp-config.php
    

    Test nginx with nginx -t before reload. Moving wp-config.php one level above the webroot is optional once nginx denies direct access.

    Next steps

    • Check nothing depends on XML-RPC (mobile app, Jetpack) before blocking it.
    • Rotate admin passwords and salts after the new admin user exists.
    • Ask for an incident-response runbook if you suspect past misuse of "admin".

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Secure Your WordPress Infrastructure

    WordPress powers over 40% of the web, making it the primary target for automated mass-exploitation. Most breaches don't happen because of poor PHP code, but because of misconfigured environments, unpatched plugins, and weak access controls. This skill turns your AI agent into a Senior WordPress Security Operations Engineer focused on infrastructure hardening and incident response.

    What it does

    • AUDIT: Performs a comprehensive assessment of your live site's security posture, including third-party plugin/theme CVE exposure, configuration gaps, and transport security.
    • HARDEN: Delivers production-ready configuration snippets (wp-config.php, .htaccess, Nginx, Security Headers) and WP-CLI commands to lock down your install.
    • INCIDENT: Provides a step-by-step containment-to-recovery runbook for compromised sites, focusing on forensics before deletion to ensure attackers don't return.

    Why use this skill?

    Unlike generic GPT prompting, this skill uses a structured 10-domain hardening framework and a dynamic scoring system (Impact / Effort) to prioritize fixes. It distinguishes between "security by obscurity" and "security by design," ensuring you implement high-value controls like 2FA and CSP over cosmetic changes. Every recommendation includes a Verify: step so you can objectively confirm the fix worked.

    Supported Environments

    Works across Managed WP hosts, VPS (Docker/CloudPanel/Coolify), and shared hosting. It prioritizes WP-CLI workflows for efficiency but provides manual alternatives for dashboard-only access.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for WordPress and WooCommerce.

    • Cannot perform direct network scanning or pen-testing.
    • No support for custom PHP code review or logic flaws.
    • Limited to WordPress-specific infrastructure, not general OS hardening.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    Network Access
    Listed4 months ago
    Updated3 days ago

    What's inside

    Frequently Asked Questions

    This skill goes beyond generic advice by providing a structured 10-domain hardening framework, production-ready configuration code, and WP-CLI commands that specifically address your site's unique CVE exposure and environment.

    The skill is designed for any Large Language Model (LLM) capable of interpreting structured diagnostic data; it performs best when given access to plugin lists, version numbers, or server configuration snippets.

    Yes, it provides optimized configurations for Nginx and Apache, as well as hardening steps for modern stacks like Docker, Coolify, and managed WordPress hosting environments.

    You receive the complete hardening framework, incident recovery runbooks, and a library of security-focused configuration templates that your agent can deploy immediately.

    Absolutely. While it prioritizes WP-CLI for automation, it includes manual dashboard-based instructions and file-level configuration steps for users on shared hosting plans.

    Yes, the skill is regularly updated to include the latest WordPress security best practices and response strategies for newly discovered vulnerabilities in the WordPress ecosystem.

    New in Security