- Home
- Skills
- DevOps & Cloud
- Vercel and Netlify Config Check
More screenshots
Works with the AI Agents you already use
Vercel and Netlify Config Check
This skill finds those and six other deploy config mistakes before you deploy, and tells you how to fix each one.
$5
Vercel and Netlify Config Check
Example session with this skill installed
Check this project with vercel-netlify-config-check.
- Read your context and instructions
- Compiled the vercel and netlify
$ python3 scripts/check_deploy_config.py examples/risky
BLOCK site/netlify.toml:8 D01 SECRET_IN_DEPLOY_CONFIG
CONTENTFUL_ACCESS_TOKEN = "<redacted>"
Why: A password, token or key is written in the deploy config: Vercel env or build.env, a route transform that sets an Authorization or API key header, Netlify [build.environment] or [context.*.environment], headers on a Netlify proxy rule, a Basic-Auth header, [dev] jwtSecret, plugin inputs, or a user:password or token inside a redirect URL. The file is committed, so everyone with the repository, its forks and old commits has the secret.
Safer: Remove the value, store it in the platform's environment variables (Vercel project settings, Netlify site configuration) and change the secret that was committed. On Vercel routes use "args": "$API_KEY" with "env": ["API_KEY"]; on Netlify proxies use signed = "ENV_VAR_NAME"; for passwords use the platform's password protection instead of a Basic-Auth line in a file.
BLOCK site/netlify.toml:16 D01 SECRET_IN_DEPLOY_CONFIG
BLOCK site/public/_headers:3 D01 SECRET_IN_DEPLOY_CONFIG
BLOCK site/public/_headers:6 D02 CORS_CREDENTIALS_ANY_ORIGIN
BLOCK site/public/_redirects:2 D03 REDIRECT_HOST_FROM_REQUEST
BLOCK vercel.json:6 D01 SECRET_IN_DEPLOY_CONFIG
BLOCK vercel.json:7 D01 SECRET_IN_DEPLOY_CONFIG
BLOCK vercel.json:37 D03 REDIRECT_HOST_FROM_REQUEST
REVIEW site/netlify.toml:18 D11 MISSING_SECURITY_HEADERS
REVIEW site/netlify.toml:21 D12 WEAK_SECURITY_HEADER
REVIEW site/public/_redirects:3 D14 PLAIN_HTTP_TARGET
REVIEW vercel.json:9 D11 MISSING_SECURITY_HEADERS
REVIEW vercel.json:13 D15 CORS_WILDCARD_WITH_CREDENTIALS
REVIEW vercel.json:20 D13 CORS_ANY_ORIGIN_ON_API
REVIEW vercel.json:27 D12 WEAK_SECURITY_HEADER
REVIEW vercel.json:28 D12 WEAK_SECURITY_HEADER
REVIEW vercel.json:33 D14 PLAIN_HTTP_TARGET
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 4 files, 4 with deploy 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
A STRIPE_SECRET_KEY left in the env block of vercel.json is readable by everyone who can see the repository, and a rewrite from /u/:id* to https://:id.example.com/ lets anyone point your domain at a site of their choice. This skill finds those and six other deploy config mistakes before you deploy, and tells you how to fix each one.
Your agent runs a scanner on your Vercel and Netlify configs: vercel.json (env, build.env, headers, redirects, rewrites, and routes with their transforms), netlify.toml (build and deploy-context environments, dev, plugin inputs, redirects with proxy headers, headers), and _headers and _redirects files (the same format Cloudflare Pages reads). It knows path parameters such as :id(\d+), Netlify splats and query placeholders, has captures and route env lists, so restricted parameters and environment references are not reported. For missing headers it looks at the whole project, including next.config, middleware and Netlify edge functions. It never deploys, builds or contacts a server. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- D01: API keys, tokens and passwords written in Vercel env or build.env, Netlify build or context environments, dev jwtSecret, plugin inputs, Netlify proxy headers, Vercel route transforms, Basic-Auth lines, or redirect URLs
- D02: Access-Control-Allow-Credentials true with Allow-Origin null or an origin copied from the request that can match any site (a capture limited to your own origins is fine)
- D03: redirects, rewrites and proxies whose target host comes from the request (https://:splat, https://:id.example.com with an unrestricted :id)
REVIEW
- D11: no X-Frame-Options or CSP frame-ancestors, or no X-Content-Type-Options nosniff, anywhere in the project's header rules
- D12: weak header values: X-Frame-Options ALLOW-FROM, frame-ancestors *, Referrer-Policy unsafe-url, an HSTS max-age under one year
- D13: Access-Control-Allow-Origin * on Vercel API routes, or with write methods or an Authorization header
- D14: redirect, rewrite or proxy targets on plain http://
- D15: Allow-Origin * with Allow-Credentials true, which browsers refuse (a broken config rather than a leak)
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 Vercel app and a Netlify site with _headers and _redirects), and the real report the scanner produces on the risky one
Limits It reads each config as written: settings made in the Vercel or Netlify dashboard (environment variables, password protection, domains), headers set in server code outside the framework files it reads, the rules in vercel.ts, bulk redirect files and what a proxied backend returns are not checked. D11 (REVIEW) appears on most projects that have not added custom security headers, and headers set in application code (helmet in an Express server, middleware outside the files it reads) are not seen. NOT FLAGGED is not a guarantee.
Static check of deploy config text. D11 checks that frame protection and nosniff are set somewhere in the project, not that every path is covered, and CORS * on API paths is reported for Vercel only, since Netlify does not add custom headers to function or proxy responses. 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 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
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example configs include clearly fake, inert tokens and passwords (NOTREAL-...) and made-up hosts for the scanner to find. Nothing is deployed or contacted.