More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Django Settings Check

    1

    Check Django settings before you deploy: DEBUG on, SECRET_KEY in code, ALLOWED_HOSTS '*', database passwords in code, missing CSRF protection, insecure cookies, HTTPS off, CORS open to all, and weak password hashers.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Django Settings Check

    Django Settings Check

    Example session with this skill installed

    Check this project with django-settings-check.

    • Read your context and instructions
    • Compiled the django settings check

    $ python3 scripts/check_django.py examples/risky
    BLOCK shop/settings.py:2 D02 SECRET_KEY_IN_CODE
    SECRET_KEY=<redacted, 41 chars>
    Why: SECRET_KEY is written in the settings file (or used as the default when the environment variable is missing). Anyone with the code can forge sessions, password reset links and signed data.
    Safer: Generate a new key, keep it only in the environment or a secrets manager, and read it with no default, so a missing key stops the app instead of falling back.

    BLOCK shop/settings.py:3 D01 DEBUG_ON
    BLOCK shop/settings.py:4 D03 ALLOWED_HOSTS_WILDCARD
    BLOCK shop/settings.py:19 D04 DATABASE_PASSWORD_IN_CODE
    BLOCK shop/settings.py:24 D05 SECRET_SETTING_IN_CODE
    REVIEW shop/settings.py:7 D11 CSRF_MIDDLEWARE_MISSING
    REVIEW shop/settings.py:26 D15 WEAK_PASSWORD_HASHER
    REVIEW shop/settings.py:27 D16 NO_PASSWORD_VALIDATION
    REVIEW shop/settings.py:29 D12 INSECURE_COOKIES
    REVIEW shop/settings.py:30 D13 HTTPS_NOT_ENFORCED
    REVIEW shop/settings.py:31 D14 CORS_ALLOWS_ALL_ORIGINS

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 1 file, 1 with Django settings 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

    One forgotten line in settings.py can show your whole configuration to visitors (DEBUG = True) or let anyone forge sessions (a SECRET_KEY in the repository). This skill finds those and nine other Django settings mistakes before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on your settings files: settings.py, a settings/ folder (base.py, production.py) and local_settings.py. It reads them with Python's own parser, so it understands real code, including settings inside if and try blocks and fallback defaults in environment lookups. It never imports or runs your settings. Development and test settings files are read but not reported. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Keys and passwords are never printed.

    What it checks

    BLOCK

    • D01: DEBUG = True, also when an environment lookup defaults to true
    • D02: a SECRET_KEY written in the file, or used as a hardcoded fallback default
    • D03: '*' in ALLOWED_HOSTS
    • D04: a database password or a database URL with a password in DATABASES
    • D05: another secret setting in the file, such as EMAIL_HOST_PASSWORD or AWS_SECRET_ACCESS_KEY

    REVIEW

    • D11: MIDDLEWARE without CsrfViewMiddleware
    • D12: session or CSRF cookies set to insecure, or the session cookie readable by JavaScript
    • D13: SECURE_SSL_REDIRECT off or SECURE_HSTS_SECONDS = 0
    • D14: django-cors-headers allowing every origin
    • D15: an MD5, SHA1, unsalted or crypt hasher first in PASSWORD_HASHERS
    • D16: an empty AUTH_PASSWORD_VALIDATORS list

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • Risky and safe example settings, and the real report the scanner produces on the risky one

    Limits Each settings file is checked on its own, so values imported with from .base import * or set by environment variables are not seen. Run python manage.py check --deploy too. NOT FLAGGED is not a guarantee.

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

    Static check of settings files. Values built at run time, environment variables and settings imported from other modules 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 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 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 settings include a clearly fake, inert key and passwords (django-insecure-not-a-real-key-0000000000, not-a-real-password, not-a-real-mail-password) for the scanner to find.

    Listed7 days ago
    Updated4 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 settings files as text with Python's own parser. It never imports them, runs manage.py or needs Django.

    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.

    New in Security