What is Next.js Security Scan?

A security scanner for Next.js applications and TypeScript or JavaScript projects. It checks source code, settings, dependencies, and environment-variable usage for common security problems.

Use it for quick, full, or targeted scans covering issues such as cross-site scripting, injection, authentication, authorization, configuration, cryptography, and Next.js-specific risks. It can also audit dependencies and look for exposed credentials.

It helps find vulnerabilities before an application is released or reviewed, including exposed secrets, unsafe code patterns, missing protection, and outdated packages with known CVEs. CVEs are public records of identified software vulnerabilities.

Next.js Security Scan — Skill for Claude Code by sugarforever

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add sugarforever/01coder-agent-skills --skill nextjs-security-scan

Clone the repo

git clone --depth 1 https://github.com/sugarforever/01coder-agent-skills

Made for: Claude Code.

Or install 01coder-skills, the plugin that ships this one along with the rest of its 23 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sugarforever/01coder-agent-skills/nextjs-security-scan/github.svg)](https://agentmods.dev/skills/sugarforever/01coder-agent-skills/nextjs-security-scan)

Your own site

<a href="https://agentmods.dev/skills/sugarforever/01coder-agent-skills/nextjs-security-scan"><img src="https://agentmods.dev/badge/skills/sugarforever/01coder-agent-skills/nextjs-security-scan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sugarforever/01coder-agent-skills/nextjs-security-scan"><img src="https://agentmods.dev/badge/skills/sugarforever/01coder-agent-skills/nextjs-security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,246 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.01246
Opus 5.5	$0.00025	$0.00498
Sonnet 5.5	$0.00013	$0.00249
Haiku 4.5	$0.00006	$0.00125

Measured 2mo ago against content hash 64210918bb03, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Next.js Security Scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/dependency-audit.sh, scripts/pattern-scanner.py, scripts/secret-scanner.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/nextjs-security-scan/SKILL.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Next.js Security Scan Skill

This skill enables comprehensive security scanning of Next.js and TypeScript/JavaScript projects based on OWASP guidelines and industry best practices.

When to Use This Skill

Security audits of Next.js applications
Code review for security vulnerabilities
Pre-deployment security checks
Dependency vulnerability assessment
Detecting hardcoded secrets and credentials

Scan Types

1. Quick Scan

Fast scan focusing on critical vulnerabilities:

Hardcoded secrets and API keys
Dangerous function usage (dangerouslySetInnerHTML, eval)
Missing authentication in Server Actions
Known vulnerable dependencies

2. Full Scan

Comprehensive security assessment covering:

All OWASP Top 10:2025 categories
XSS vulnerability patterns
Injection vulnerabilities (SQL, NoSQL, Command)
Authentication and authorization flaws
Security misconfigurations
Cryptographic failures
Next.js-specific vulnerabilities
Dependency audit (CVE check)
Environment variable exposure

3. Targeted Scan

Focus on specific vulnerability categories:

--xss - Cross-site scripting patterns
--injection - SQL/NoSQL/Command injection
--auth - Authentication/authorization issues
--secrets - Hardcoded credentials
--deps - Dependency vulnerabilities
--nextjs - Next.js specific issues

Scan Procedure

Step 1: Project Discovery

Identify project type (Next.js App Router, Pages Router, or plain React)
Locate configuration files (next.config.js, package.json, .env*)
Map the codebase structure

Step 2: Dependency Audit

Run the dependency audit script:

./scripts/dependency-audit.sh

Or manually:

npm audit --json
# or
yarn audit --json

Step 3: Secret Scanning

Scan for hardcoded secrets:

python scripts/secret-scanner.py /path/to/project

Important: Environment File Handling

By default, real .env files are SKIPPED (.env, .env.local, .env.production, etc.)
These files contain actual secrets and should not be in version control
Only .env.example and .env.template files are analyzed for documentation quality
Use --include-env-files flag only if explicitly requested by user

Read the full file on GitHub · 156 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 156 lines · 63 tokens per session scan A 64210918bb03

Subscribe to this mod's changes

Next.js Security Scan is a skill published in the GitHub repository sugarforever/01coder-agent-skills (139 stars, last pushed 18d ago), licensed MIT. It adds 63 tokens to every session and 1,246 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.