More screenshots
Works with the AI Agents you already use
nginx Config Safety Check
It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach.
$5
nginx Config Safety Check
Example session with this skill installed
Check this project with nginx-config-safety-check.
- Read your context and instructions
- Compiled the nginx config safety
$ python3 scripts/check_nginx.py examples/risky
BLOCK nginx.conf:8 W02 OLD_TLS_PROTOCOL
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
Why: ssl_protocols allows SSLv3, TLS 1.0 or TLS 1.1. These versions have known attacks and are rejected by modern browsers and compliance checks.
Safer: Use ssl_protocols TLSv1.2 TLSv1.3;
BLOCK nginx.conf:14 W03 ALIAS_PATH_TRAVERSAL
BLOCK nginx.conf:18 W01 DIRECTORY_LISTING_ON
BLOCK nginx.conf:22 W04 PROXY_TARGET_FROM_REQUEST
REVIEW nginx.conf:3 W14 UNLIMITED_BODY_SIZE
REVIEW nginx.conf:5 W12 NO_HSTS
REVIEW nginx.conf:5 W15 SECURITY_HEADERS_MISSING
REVIEW nginx.conf:9 W13 WEAK_CIPHERS
REVIEW nginx.conf:10 W11 SERVER_TOKENS_ON
REVIEW nginx.conf:26 W16 STATUS_PAGE_OPEN
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 1 file, 1 with nginx 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
location /static with alias /var/www/static/ looks harmless, but /static../ then reads files outside the folder. This skill finds that classic nginx bug and nine other risky settings, and tells you how to fix each one.
Your agent runs a scanner on nginx.conf, conf.d and sites-enabled files. Files are checked together and include lines inside the scanned folder are followed, using nginx's real add_header inheritance rules. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach.
What it checks
BLOCK
- W01: autoindex on
- W02: SSLv3, TLS 1.0 or TLS 1.1 allowed
- W03: the alias off-by-slash path traversal
- W04: proxy_pass to a host taken from the request
REVIEW
- W11: server_tokens not turned off
- W12: an HTTPS server without HSTS
- W13: weak ciphers such as RC4 or 3DES
- W14: client_max_body_size 0
- W15: no nosniff and framing headers
- W16: stub_status with no deny rule
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, and the real report the scanner produces on the risky one
Limits It reads config text. It does not follow includes outside the scanned folder, and it cannot see TLS settings on a load balancer or CDN in front of nginx. 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 nginx config text. Includes outside the scanned folder, map blocks and Lua code are not evaluated. 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
- Software
python3 (3.9 or newer)
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls.