- Home
- Skills
- DevOps & Cloud
- Caddyfile Check
More screenshots
Works with the AI Agents you already use
Caddyfile Check
Check Caddyfiles and Caddy JSON before you reload: an admin API on 0.0.0.0:2019, tls_insecure_skip_verify, file_server on home or system folders, DNS tokens in the config, tls internal on public domains and .git served.
$5
Caddyfile Check
Example session with this skill installed
Check this project with caddyfile-check.
- Read your context and instructions
- Compiled the caddyfile check
$ python3 scripts/check_caddy.py examples/risky
BLOCK Caddyfile:4 C04 SECRET_IN_CONFIG
acme_dns cloudflare <redacted>
Why: A token, password or key is written in the config: a DNS provider token (dns cloudflare ..., acme_dns), an ACME EAB MAC key, a storage password, an Authorization or API key header, a matcher that compares a header with a fixed key, or a URL with user:password@. Everyone who can read the repository or the server's config files can use it.
Safer: Read it from the environment at run time (dns cloudflare {env.CLOUDFLARE_API_TOKEN}, header_up X-Api-Key {env.API_KEY}), and change the secret that was committed.
BLOCK edge/caddy.json:3 C01 ADMIN_API_EXPOSED
BLOCK sites/shop.caddy:14 C02 TLS_CHECKS_OFF
BLOCK sites/shop.caddy:23 C04 SECRET_IN_CONFIG
BLOCK sites/tools.caddy:3 C03 SENSITIVE_FOLDER_SERVED
REVIEW Caddyfile:6 C16 ALL_PROXIES_TRUSTED
REVIEW edge/caddy.json:19 C17 CREDENTIALS_LOGGED
REVIEW sites/shop.caddy:9 C18 UNSUPPORTED_TLS_PROTOCOL
REVIEW sites/shop.caddy:19 C15 SITE_WITHOUT_SECURITY_HEADERS
REVIEW sites/shop.caddy:20 C14 CORS_ORIGIN_REFLECTED
REVIEW sites/tools.caddy:9 C11 UNTRUSTED_CERT_ON_PUBLIC_SITE
REVIEW sites/tools.caddy:10 C13 DOTFILES_SERVED
REVIEW sites/tools.caddy:13 C12 PLAIN_HTTP_SITE
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 4 files, 4 with Caddy 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
admin 0.0.0.0:2019 lets anyone who can reach port 2019 replace your whole Caddy config with no password, and a file_server with no root serves the folder Caddy runs in, .git and .env included. This skill finds those and ten other Caddy config mistakes before you reload or deploy, and tells you how to fix each one.
Your agent runs a scanner on your project: files named Caddyfile (also Caddyfile.prod and similar), .caddyfile and .caddy, and Caddy JSON configs. It reads Caddyfile syntax the way Caddy does: the global options block, snippets and import (also of other files in the folder, so import sites/.caddy is followed), several addresses per site, a single site without braces, matchers, comments, quoted strings, heredocs and {env.} placeholders. It follows Caddy's real defaults: the admin API on localhost:2019, no security headers and no HSTS unless you add them, the active Caddyfile hidden from file_server but other dotfiles not. The minimal Caddyfiles from the Caddy documentation and the Docker image's default Caddyfile pass clean. It never runs Caddy or calls its admin API. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- C01: the admin API on :2019, 0.0.0.0, a LAN IP or a host name instead of localhost or a unix socket
- C02: tls_insecure_skip_verify on a reverse_proxy backend, and insecure_secrets_log
- C03: file_server on /, /etc, /var, a home folder, a .ssh folder or Caddy's own certificate storage
- C04: DNS provider tokens, API keys, passwords, EAB keys and Authorization headers written in the config
REVIEW
- C11: tls internal, local_certs or a staging ACME CA on a public domain
- C12: http:// or :80 public sites that serve content, and auto_https off
- C13: file_server with no root or root . while nothing hides .git and .env
- C14: CORS that copies any Origin into Access-Control-Allow-Origin with credentials allowed
- C15: a public site without the security headers the other sites in the config send
- C16: trusted_proxies set to 0.0.0.0/0 or ::/0
- C17: log_credentials, which writes cookies and Authorization headers to the access log
- C18: protocols tls1.0 or tls1.1, which Caddy v2 does not support and refuses to load
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 project (a Caddyfile with imported site files and a Caddy JSON config), and the real report the scanner produces on the risky one
Limits It reads the config files as written. Values from environment variables (CADDY_ADMIN, {env.*}), command-line flags, config pushed through the admin API, caddy-docker-proxy labels and imports of files outside the scanned folder are not checked, and headers sent by the app behind reverse_proxy are not visible to it. 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 DevOps & Cloud.
Static check of Caddy config text. Environment variables such as CADDY_ADMIN, command-line flags, config pushed through the admin API, Docker labels and imports outside the scanned folder are not checked. Relative root folders are looked up next to the config file. NOT FLAGGED is not a guarantee.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert tokens (not-a-real-..., EXAMPLE) for the scanner to find. It is never run or deployed.