Skip to content
Skills Library
Security · Review & audit

frontend-security

/frontend-security

Audit frontend codebases for security vulnerabilities and bad practices. Use when performing security reviews, auditing code for XSS/CSRF/DOM vulnerabilities, checking Content Security Policy configurations, validating input handling, reviewing file upload security, or examining Node.js/NPM dependencies. Target frameworks include web platform (vanilla HTML/CSS/JS), React, Astro, Twig templates, Node.js, and Bun. Based on OWASP security guidelines.

Licence
MIT
Last repository change
24.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
12
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Audit frontend codebases for security vulnerabilities and bad practices. Use when performing security reviews, auditing code for XSS/CSRF/DOM vulnerabilities, checking Content Security Policy configurations, validating input handling, reviewing file upload security, or examining Node.js/NPM dependencies. Target frameworks include web platform (vanilla HTML/CSS/JS), React, Astro, Twig templates, Node.js, and Bun. Based on OWASP security guidelines.

Original author description

Audit frontend codebases for security vulnerabilities and bad practices. Use when performing security reviews, auditing code for XSS/CSRF/DOM vulnerabilities, checking Content Security Policy configurations, validating input handling, reviewing file upload security, or examining Node.js/NPM dependencies. Target frameworks include web platform (vanilla HTML/CSS/JS), React, Astro, Twig templates, Node.js, and Bun. Based on OWASP security guidelines.

How it works

  1. Workflow
  2. Reference Routing
  3. Severity
Original SKILL.md headings · 54 lines, 393 words
SKILL.md preview
---
name: frontend-security
description: Audit frontend codebases for security vulnerabilities and bad practices. Use when performing security reviews, auditing code for XSS/CSRF/DOM vulnerabilities, checking Content Security Policy configurations, validating input handling, reviewing file upload security, or examining Node.js/NPM dependencies. Target frameworks include web platform (vanilla HTML/CSS/JS), React, Astro, Twig templates, Node.js, and Bun. Based on OWASP security guidelines.
---

# Frontend Security Audit Skill

Audit frontend-adjacent code by mapping trust boundaries, tracing untrusted data into dangerous
sinks, and using searches as supporting evidence. Cover browser/frontend concerns first, then route
related server, package, authentication, and upload findings to the relevant reference.

## Workflow

1. Map routes, rendering models, APIs, authentication/session boundaries, third-party scripts,
   uploads, package-manager entry points, and deployment assumptions.
2. List untrusted sources such as URL parameters, forms, storage, `postMessage`, responses, files,
   cookies, headers, and package metadata. Trace them to DOM, navigation, command, filesystem,
   database, network, and log sinks.
3. Load `references/audit-workflow.md` for focused evidence searches. Treat matches as leads, not
   proof; use AST-aware tooling where syntax or multiline structure matters.
4. Review output encoding, sanitization, CSP, CSRF, token storage, input validation, uploads,
   dependencies, and framework escape hatches.
5. Rate the confirmed finding from exploitability, impact, reachability, required privileges, user
   interaction, data sensitivity, and compensating controls.
6. Report the affected trust boundary, evidence, exploit scenario, severity rationale, remediation,
   and authoritative reference using the template in `references/audit-workflow.md`.

## Reference Routing

| Finding area                                               | Load                                 |
| ---------------------------------------------------------- | ------------------------------------ |
| Browser XSS, unsafe URLs, tabnabbing, HTML injection       | `references/xss-prevention.md`       |
| DOM sinks, clobbering, postMessage, client storage         | `references/dom-security.md`         |
| CSP headers, nonces, hashes, Trusted Types                 | `references/csp-configuration.md`    |
| Cookie auth, forms, state-changing requests                | `references/csrf-protection.md`      |
| URL, number, date, schema, and path validation             | `references/input-validation.md`     |
| React, Astro, Twig, SSR, hydration, templates              | `references/framework-patterns.md`   |
| Uploads, downloads, archives, quarantine                   | `references/file-upload-security.md` |
| JWT lifecycle, storage, fingerprints, refresh flows        | `references/jwt-security.md`         |
| Node runtime, npm supply chain, scripts, command execution | `references/nodejs-npm-security.md`  |

Name boundaries precisely, for example “browser-to-API CSRF,” “frontend-triggered upload
processing,” or “package-script supply-chain risk.” State scope limits: route deep backend
authorization, database, infrastructure, malware, and incident-response work to specialists.

## Severity

- **Critical**: likely high-impact exploit such as unauthenticated account takeover, privileged
  stored XSS, production credential exposure, or reachable remote code execution.
- **High**: plausible exploit with meaningful user, data, integrity, or supply-chain impact.
- **Medium**: real weakness with limited reach, prerequisites, lower sensitivity, or meaningful
  compensating controls.
- **Low**: hard-to-exploit or defense-in-depth gap, deprecated pattern, or hygiene issue.

Always record why the project-specific evidence supports the chosen severity. Consider attacker
capability, interaction, privileges, production reachability, persistence, blast radius, and
existing controls. Do not assign severity from a search result alone.
Files in this package (12)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB
  • references/audit-workflow.md 3 KB
  • references/csp-configuration.md 7 KB
  • references/csrf-protection.md 11 KB
  • references/dom-security.md 7 KB
  • references/file-upload-security.md 19 KB
  • references/framework-patterns.md 7 KB
  • references/input-validation.md 11 KB
  • references/jwt-security.md 11 KB
  • references/nodejs-npm-security.md 9 KB
  • references/xss-prevention.md 6 KB

Versions

RepositoryScoreLicence
This page · schalkneethling/create-project-calavera100MIT
reddygopalkrishna/developer-agent-skills100MIT
susorov/agent-skills90MIT
IbrahimCodeur/saas-blind-security90MIT
j4flmao/agent-skills90MIT

Database snapshot: 13.11.2026 · package version f62644dcd1d6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90security-audit
    Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.
  • 100fec-security-review
    Use when reviewing frontend security risks such as XSS, CSRF, sensitive data exposure, unsafe DOM APIs, untrusted user input, authentication/token handling, payment flows, file upload, CSP, dependency risk, or third-party scripts; Chinese triggers include security review, security check.
  • 90security-audit
    Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.
  • 100code-review-security
    Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention,…
  • 100security
    Security auditing for code vulnerabilities (OWASP Top 10, XSS, SQL injection) and dependency scanning (pnpm audit, Snyk). Use when handling user input, adding authentication, before deployments, or resolving CVEs.
  • 100security
    Security auditing for code vulnerabilities (OWASP Top 10, XSS, SQL injection) and dependency scanning (pnpm audit, Snyk). Use when handling user input, adding authentication, before deployments, or resolving CVEs.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.