More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Next.js Config Check

    1

    Anything in a NEXT_PUBLIC_ variable is copied into the JavaScript every visitor downloads, so a secret key there is public the moment you deploy.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Next.js Config Check

    Next.js Config Check

    Example session with this skill installed

    Check this project with nextjs-config-check.

    • Read your context and instructions
    • Compiled the next js config

    $ python3 scripts/check_nextjs.py examples/risky
    BLOCK .env.production:4 N01 SECRET_IN_PUBLIC_ENV
    NEXT_PUBLIC_STRIPE_SECRET_KEY=<redacted, 24 chars>
    Why: A secret is in a NEXT_PUBLIC_ variable (or VITE_, REACT_APP_, EXPO_PUBLIC_ and similar). Next.js copies every NEXT_PUBLIC_ value into the JavaScript sent to browsers at build time, so anyone can read it in the page source.
    Safer: Drop the public prefix and read the value only in server code (route handlers, server components, server actions). Rotate the secret, because built pages already contain it.

    BLOCK .env.production:5 N01 SECRET_IN_PUBLIC_ENV
    BLOCK .env.production:7 N03 WEAK_AUTH_SECRET
    BLOCK next.config.js:17 N02 SECRET_IN_CONFIG_ENV
    REVIEW auth.ts:6 N16 RISKY_AUTH_OPTION
    REVIEW auth.ts:8 N16 RISKY_AUTH_OPTION
    REVIEW next.config.js:4 N11 PUBLIC_SOURCE_MAPS
    REVIEW next.config.js:6 N12 BUILD_CHECKS_OFF
    REVIEW next.config.js:9 N13 OPEN_IMAGE_PROXY
    REVIEW next.config.js:10 N14 SVG_WITHOUT_CSP
    REVIEW next.config.js:13 N15 SERVER_ACTIONS_ANY_ORIGIN

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 3 files, 3 with Next.js 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

    Anything in a NEXT_PUBLIC_ variable is copied into the JavaScript every visitor downloads, so a secret key there is public the moment you deploy. This skill finds that and eight other Next.js configuration mistakes before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on your next.config (js, mjs, ts), your .env files and your NextAuth or Auth.js config (auth.ts, [...nextauth] routes). It reads JavaScript and TypeScript with comments removed and strings kept, and knows which public keys are meant to be public (Stripe publishable keys, Supabase anon keys, Firebase and Maps keys). It never runs Node or Next.js. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • N01: a secret in a NEXT_PUBLIC_ (or VITE_, REACT_APP_, EXPO_PUBLIC_) variable
    • N02: a secret listed under env or publicRuntimeConfig in next.config
    • N03: a sample or short NEXTAUTH_SECRET or AUTH_SECRET

    REVIEW

    • N11: productionBrowserSourceMaps on
    • N12: TypeScript or ESLint errors ignored in builds
    • N13: images.remotePatterns open to every host
    • N14: dangerouslyAllowSVG without a CSP
    • N15: Server Actions allowedOrigins '*'
    • N16: NextAuth debug or allowDangerousEmailAccountLinking on

    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 (next.config, .env and auth.ts), and the real report the scanner produces on the risky one

    Limits It reads files as written: variables set in your hosting provider, middleware, route handlers and component code are not checked. NOT FLAGGED is not a guarantee.

    Static check of config and env files. Hosting-provider variables and application code 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

    Requires

    Node.js

    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 .env files include clearly fake, inert values (not-a-real-stripe-secret) 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 next.config, .env and auth files as text. It never runs Node, npm or Next.js.

    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 project with next.config, .env and auth files, and the real report the scanner prints on the risky example.

    New in Frontend & Web Apps