nextjs-security-review
Skill1 starsChanged 6 months agoMITView on GitHub
Use when a Next.js project or security audit involves App Router, route handlers, middleware, auth, validation, headers, environment variables, deployment, logging, redirects, SSRF, uploads, or rate limits.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- wilfreud/skills-or-somethingtheir own version, first seen Aug 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- wilfreud/skills-or-something★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms.txtllms.txt
- ai-app-security-reviewSkill
- codeaudit-orchestratorSkill
- codeauditSkill
- docs-claims-evidence-reviewSkill
- enterprise-code-qualitySkill
- github-issue-pr-workflowSkill
- official-docs-groundingSkill
- python-backend-qualitySkill
- python-mcp-server-qualitySkill
- refactor-with-testsSkill
- skill-supply-chain-auditorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Use concrete files such as middleware.ts, app/api//route.ts, next.config.*, env modules, tests, and security docs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Next.js Security Review
Required Checks
- App Router conventions and server/client boundaries.
- Route handlers and server actions for input validation.
- Auth and authorization checks on sensitive paths.
- Middleware coverage or documented route-level alternatives.
- Rate limiting on public mutation and AI/model routes.
- Security headers and deployment-layer header evidence.
- Environment validation and client/server secret separation.
- Unsafe redirects, SSRF, file uploads, and raw provider error leakage.
- Logging that may expose headers, cookies, tokens, requests, or model/provider errors.
Evidence
Use concrete files such as middleware.ts, app/api/**/route.ts, next.config.*, env modules, tests, and security docs. If a control is missing, say missing rather than assuming it exists elsewhere.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.