More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Nuxt Vue Safety Check

    1

    One openaiApiKey under runtimeConfig.public, filled at run time from NUXT_PUBLIC_OPENAI_API_KEY, sends your key to every visitor in the page payload.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Nuxt Vue Safety Check

    Nuxt Vue Safety Check

    Example session with this skill installed

    Check this project with nuxt-vue-safety-check.

    • Read your context and instructions
    • Compiled the nuxt vue safety

    $ python3 scripts/check_nuxt.py examples/risky
    BLOCK .env.example:5 N01 SECRET_EXPOSED_TO_BROWSER
    NUXT_PUBLIC_OPENAI_API_KEY=
    Why: A secret sits where Nuxt sends it to the browser: a runtimeConfig.public (or runtimeConfig.app) key whose name says secret, password, private or service role or names an AI or other paid API key, or whose value is a secret key or a secret environment variable; a NUXT_PUBLIC_ variable like that in a .env file (it overrides runtimeConfig.public at run time); a secret in app.config, which Nuxt's docs say is exposed to the client bundle; or a secret key written in a component or composable. Every visitor can read these values in the page payload or the JavaScript files.
    Safer: Move the secret to a private runtimeConfig key (runtimeConfig: { stripeSecretKey: '' }), set it on the server with NUXT_STRIPE_SECRET_KEY, and use it only in server/ routes that the app calls. Keep only publishable or anon keys in public. Rotate a secret that was exposed.

    BLOCK app/pages/login.vue:13 N04 REDIRECT_TO_URL_VALUE
    BLOCK app/pages/search.vue:8 N03 V_HTML_WITH_URL_DATA
    BLOCK nuxt.config.ts:14 N02 LITERAL_SECRET_IN_NUXT_CONFIG
    BLOCK nuxt.config.ts:18 N01 SECRET_EXPOSED_TO_BROWSER
    BLOCK server/api/auth/callback.get.ts:5 N04 REDIRECT_TO_URL_VALUE
    REVIEW app/components/AuthorBio.vue:8 N16 V_HTML_FROM_UNCHECKED_VALUE
    REVIEW app/composables/useAuth.ts:5 N13 PLAIN_HTTP_API_CALL
    REVIEW app/composables/useAuth.ts:9 N14 TOKEN_READABLE_BY_SCRIPTS
    REVIEW app/pages/account.vue:4 N15 PRIVATE_RUNTIME_CONFIG_IN_APP_CODE
    REVIEW app/pages/login.vue:5 N14 TOKEN_READABLE_BY_SCRIPTS
    REVIEW app/pages/posts/[id].vue:9 N16 V_HTML_FROM_UNCHECKED_VALUE
    REVIEW nuxt.config.ts:10 N11 CLIENT_SOURCE_MAPS
    REVIEW nuxt.config.ts:17 N13 PLAIN_HTTP_API_CALL
    REVIEW nuxt.config.ts:26 N12 CORS_ANY_ORIGIN_WITH_CREDENTIALS
    REVIEW server/api/auth/callback.get.ts:4 N14 TOKEN_READABLE_BY_SCRIPTS
    REVIEW server/middleware/cors.ts:5 N12 CORS_ANY_ORIGIN_WITH_CREDENTIALS

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

    One openaiApiKey under runtimeConfig.public, filled at run time from NUXT_PUBLIC_OPENAI_API_KEY, sends your key to every visitor in the page payload. One v-html="route.query.q" on a search page lets anyone send a link that runs scripts as your site. This skill finds those and eight other Nuxt and Vue mistakes before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on nuxt.config, app.config, your .env files (including .env.example), every .vue component and page, and the composables, plugins, route middleware, stores and server routes beside them. It knows which runtimeConfig keys are public, follows values from the URL (useRoute, $route, to.query in middleware, getQuery on the server) and from useFetch, useAsyncData and $fetch through the variables that hold them and through v-for aliases, skips comments, and accepts the usual fixes written in code (DOMPurify.sanitize, httpOnly: true, a startsWith('/') check that also rejects // and backslashes, an origin or allow-list check). Public keys such as apiBase, Firebase and VueFire config, Stripe publishable keys, Mapbox pk. tokens and Algolia search keys are left alone, and the default Nuxt starter project passes clean. It never runs Nuxt or your app. 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: secrets sent to the browser (secret-named or secret-valued runtimeConfig.public keys, NUXT_PUBLIC_ variables, app.config, secret keys in components)
    • N02: literal secrets in nuxt.config (runtimeConfig or module options, database URLs with a password)
    • N03: v-html or innerHTML with route query, params or hash data and no sanitizer
    • N04: redirects to URL values (navigateTo with external: true, window.location, window.open, sendRedirect with getQuery) without a check that rejects // and other sites

    REVIEW

    • N11: client source maps (sourcemap true, sourcemap.client true, or vite.build.sourcemap while client maps are on)
    • N12: CORS that allows credentials from any origin (route rules, handleCors options, an Origin header copied back)
    • N13: plain http:// API calls to public hosts ($fetch, useFetch, baseURL, apiBase, routeRules proxy)
    • N14: tokens readable by scripts (localStorage, useCookie or setCookie without httpOnly, document.cookie)
    • N15: private runtimeConfig secrets read in components, pages or composables
    • N16: v-html with API data, Markdown output or a value whose source the scanner cannot see

    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 Nuxt project (nuxt.config.ts, .env.example, pages, a component, a composable and server routes), and the real report the scanner produces on the risky one

    Limits It reads each file on its own: values passed as props or through stores, checks inside helpers in other files, settings from Nuxt layers or modules, and the built .output folder are not followed. The nuxt-security module, Content Security Policy headers and dependency vulnerabilities are not checked. NOT FLAGGED is not a guarantee.

    Static check of config, .env and source text. Values passed between files, Nuxt layers and modules, Content Security Policy and dependency vulnerabilities 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 .env.example files list variable names with empty values, and the one literal secret in the risky nuxt.config is a fake marked EXAMPLE. Nothing is 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 nuxt.config, .vue files and composables as text. It never runs Nuxt, npm or a browser.

    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 Nuxt app, and the real report the scanner prints on the risky example.

    New in Frontend & Web Apps