More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Home Assistant Config Check

    1

    One db_url: mysql://homeassistant:password@core-mariadb line, or one Wi-Fi password in an ESPHome file, is enough to leak your passwords the day you push your config to GitHub.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Home Assistant Config Check

    Home Assistant Config Check

    Example session with this skill installed

    Check this project with home-assistant-config-check.

    • Read your context and instructions
    • Compiled the home assistant config

    $ python3 scripts/check_hass.py examples/risky
    BLOCK configuration.yaml:19 H04 TRUSTED_NETWORK_IS_INTERNET
    - "::/0"
    Why: The trusted_networks login provider trusts 0.0.0.0/0, ::/0 or a similar huge range of internet addresses. Anyone who can reach Home Assistant from there picks a user and is logged in without a password, and multi-factor authentication does not take part in that login.
    Safer: Trust only your own LAN ranges (for example 192.168.1.0/24 and fd00::/8), limit the users with trusted_users, keep type: homeassistant for everyone else, and use a VPN or Home Assistant Cloud for access from outside.

    BLOCK configuration.yaml:27 H03 PROXY_TRUSTS_EVERYONE
    BLOCK configuration.yaml:31 H01 SECRET_WRITTEN_INLINE
    BLOCK configuration.yaml:41 H01 SECRET_WRITTEN_INLINE
    BLOCK esphome/garage-door.yaml:10 H01 SECRET_WRITTEN_INLINE
    BLOCK esphome/garage-door.yaml:14 H01 SECRET_WRITTEN_INLINE
    BLOCK esphome/garage-door.yaml:18 H01 SECRET_WRITTEN_INLINE
    BLOCK packages/nas_backup.yaml:21 H01 SECRET_WRITTEN_INLINE
    BLOCK secrets.yaml:2 H02 SECRETS_NOT_IGNORED
    REVIEW automations.yaml:9 H15 WEBHOOK_OPEN_TO_INTERNET
    REVIEW configuration.yaml:10 H12 EXTERNAL_URL_NOT_HTTPS
    REVIEW configuration.yaml:13 H16 BROAD_ALLOWLISTED_FOLDER
    REVIEW configuration.yaml:20 H11 TRUSTED_NETWORK_BYPASS
    REVIEW configuration.yaml:28 H13 LOGIN_BANS_OFF
    REVIEW packages/nas_backup.yaml:8 H14 TEMPLATE_IN_COMMAND
    REVIEW packages/nas_backup.yaml:13 H14 TEMPLATE_IN_COMMAND
    REVIEW packages/nas_backup.yaml:19 H17 TLS_CHECK_OFF

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

    BLOCK configuration.yaml

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

    About this skill

    One db_url: mysql://homeassistant:password@core-mariadb line, or one Wi-Fi password in an ESPHome file, is enough to leak your passwords the day you push your config to GitHub. And trusted_proxies: 0.0.0.0/0 lets anyone on the internet choose the IP address Home Assistant sees, so IP bans and local-only webhooks stop protecting you. This skill finds those and nine other Home Assistant configuration mistakes before you share, commit or expose your setup, and tells you how to fix each one.

    Your agent runs a scanner on your Home Assistant config folder: configuration.yaml, automations.yaml, scripts, packages, blueprints, files pulled in with !include and !include_dir_*, and ESPHome device files kept beside them. It understands !secret, !include, !env_var and !input as references, not values, knows both trigger styles (trigger: webhook and platform: webhook), reads included files that hold only an http: block, an auth provider list or a list of platforms, and skips YAML that is not Home Assistant's (CI workflows, Docker Compose, Kubernetes). It checks .gitignore rules itself, including the common "ignore everything, then allow *.yaml" style. It never runs Home Assistant, calls its API or connects to anything. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • H01: passwords, tokens and keys written inline instead of !secret: secret-named keys, passwords in db_url and rtsp:// camera URLs, Authorization headers, tokens in URLs, long-lived access tokens and ESPHome API encryption keys
    • H02: secrets.yaml, .storage or .cloud in a git repository with no .gitignore rule covering it
    • H03: use_x_forwarded_for with trusted_proxies open to the whole internet (0.0.0.0/0, ::/0)
    • H04: a trusted_networks login provider that trusts the whole internet

    REVIEW

    • H11: allow_bypass_login: true, or public addresses in trusted_networks
    • H12: external_url on plain http:// for an internet host
    • H13: ip_ban_enabled: false, login_attempts_threshold: -1, or no threshold behind a reverse proxy or TLS
    • H14: templates inside shell_command and command_line commands
    • H15: webhook triggers with local_only: false
    • H16: allowlist_external_dirs that open /, /config, /etc, /root or /home
    • H17: verify_ssl: false for https hosts on the internet

    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 config folder (configuration.yaml, secrets.yaml, automations.yaml, a package, an ESPHome device and .gitignore), and the real report the scanner produces on the risky one

    Limits It reads each YAML file as written and does not merge !include files or resolve !secret values. Settings made in the UI live in .storage and are not read; from Home Assistant 2026.8 that includes the http: settings, which are imported once from YAML into Settings > System > Network, so check them there too. Users, MFA, port forwarding and add-ons are not checked. NOT FLAGGED is not a guarantee.

    Static check of Home Assistant and ESPHome YAML text. Settings stored in .storage through the UI, the running instance and the network around it are not checked. 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 config folder includes clearly fake, inert passwords, tokens and keys (NOTREAL-...) for the scanner to find. Nothing in it is ever run.

    Listed5 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 configuration.yaml, packages and automations as text. It never calls Home Assistant and never reads values from secrets.yaml into the report.

    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 Home Assistant config, and the real report the scanner prints on the risky example.

    New in Security