More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    WordPress Config Check

    1

    Check wp-config.php before a site goes live: sample keys and salts, PHP errors shown to visitors, a public debug.log, wp-config.php.bak copies, the dashboard code editor, and weak database and update settings.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    WordPress Config Check

    WordPress Config Check

    Example session with this skill installed

    Check this project with wordpress-config-check.

    • Read your context and instructions
    • Compiled the wordpress config check

    $ python3 scripts/check_wpconfig.py examples/risky
    BLOCK wp-config.php:8 V01 SAMPLE_KEYS_AND_SALTS
    4 of the 8 keys and salts still use the sample phrase 'put your unique phrase here'
    Why: The authentication keys and salts still say 'put your unique phrase here', the text from wp-config-sample.php. Everyone knows it, so login cookies and nonces can be forged.
    Safer: Generate new values with the WordPress salt generator (api.wordpress.org/secret-key/1.1/salt/) or wp config shuffle-salts and paste them in. Everyone is logged out once.

    BLOCK wp-config.php:19 V02 ERRORS_SHOWN_TO_VISITORS
    BLOCK wp-config.php:20 V03 PUBLIC_DEBUG_LOG
    BLOCK wp-config.php.bak V04 CONFIG_BACKUP_COPY
    REVIEW wp-config.php:4 V14 DATABASE_ROOT_USER
    REVIEW wp-config.php:5 V15 EMPTY_DATABASE_PASSWORD
    REVIEW wp-config.php:12 V16 WEAK_KEYS_AND_SALTS
    REVIEW wp-config.php:21 V11 DASHBOARD_CODE_EDITOR_ON
    REVIEW wp-config.php:22 V12 ADMIN_SSL_OFF
    REVIEW wp-config.php:23 V13 AUTO_UPDATES_OFF

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 2 files, 2 with WordPress config content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

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

    About this skill

    WordPress sites are often broken into through their configuration, not their code: salts that still say 'put your unique phrase here', a wp-config.php.bak that the web server hands out as plain text, or a debug.log anyone can download. This skill finds those and seven other wp-config mistakes before a site goes live or is handed over, and tells you how to fix each one.

    Your agent runs a scanner on your site folder. It reads wp-config.php, wp-config-<name>.php files, Bedrock's config/application.php and environment files, and backup copies of wp-config.php. It understands PHP comments and strings, so a commented-out define does not count and salts full of symbols are read correctly. It never runs PHP or WordPress. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Salts and passwords are never printed.

    What it checks

    BLOCK

    • V01: keys and salts that still say 'put your unique phrase here'
    • V02: WP_DEBUG on without WP_DEBUG_DISPLAY turned off, so errors show on pages
    • V03: WP_DEBUG_LOG writing to wp-content/debug.log or elsewhere under the web root
    • V04: a copy of wp-config.php that does not end in .php (.bak, .old, .orig, .save, .swp, .txt, ~ and similar)

    REVIEW

    • V11: DISALLOW_FILE_EDIT not set, so admins can edit theme and plugin PHP in the dashboard
    • V12: FORCE_SSL_ADMIN set to false
    • V13: automatic updates turned off (AUTOMATIC_UPDATER_DISABLED or WP_AUTO_UPDATE_CORE false)
    • V14: DB_USER is root
    • V15: an empty DB_PASSWORD
    • V16: keys or salts shorter than 32 characters, or repeated

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example wp-config.php, a backup copy to find, and the real report the scanner produces on the risky example

    Limits It reads define() calls as written, so constants set in included files, values from the database and server rules that block files are not seen. NOT FLAGGED is not a guarantee.

    Static check of PHP config text. Code is not run, so values built at run time and constants set in included files are not seen. NOT FLAGGED is not a guarantee.

    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 any payment.

    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 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example folder includes a backup file (wp-config.php.bak) with a clearly fake, inert password (not-a-real-password) for the scanner to find.

    Listed7 days ago
    Updated5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads your config files as text. It never runs PHP or WordPress and never connects to your database or server.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example wp-config.php and a backup copy, and the real report the scanner prints on the risky example.

    New in Security