frontend security audit
Perform evidence-based frontend security audits for XSS, CSP gaps, and insecure cookies with ranked remediation plans.
$5
Works with the AI Agents you already use
frontend security audit
Example session with this skill installed
Audit the src/components/search directory for XSS and check if our CSP in the meta tags is actually protecting us from inline script execution.
- Read your context and instructions
- Compiled the frontend security audit
Audit complete for src/components/search.
Confirmed Findings
[FSA-001] Critical: Reflected XSS in SearchBar.tsx via 'query' param. No encoding at sink.
[FSA-002] Medium: Insecure CSP meta tag. 'unsafe-inline' detected in script-src.
Proposed Fixes
- Sanitize 'query' using DOMPurify.
- Move CSP to headers.
Approve?
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Static analysis tools produce too much noise, while manual security reviews are slow and easy to miss deep data-flow vulnerabilities. Frontend developers often struggle to bridge the gap between finding a potential XSS pattern and actually proving it is exploitable in their specific framework context.
What it does
- Maps the entire frontend attack surface, including route entry points, DOM sinks, and third-party script integrations.
- Traces data flow from attacker-controlled sources through transformations to context-sensitive sinks to confirm exploitability.
- Audits Content Security Policy (CSP) delivery, verifying header-level enforcement and identifying bypass-prone source lists.
- Inspects cookie attributes (Secure, HttpOnly, SameSite) and frontend-adjacent session management for leakage risks.
- Generates a severity-ranked report using a structured rubric and provides a granular, one-to-one patch plan for approval.
Frameworks & tools
Works with modern frontend frameworks (React, Vue, Svelte), server-rendered paths, and build systems. Utilizes Python-based scanning scripts for inventory and manual repository search for deep tracing.
Why this beats prompting it yourself
Generic prompts often hallucinate security risks or suggest broad, breaking changes. This skill follows a strict operating contract that enforces read-only discovery, evidence-based validation, and mandatory approval gates before any code is modified.
Use cases
- Perform a pre-release security audit of a new frontend module or component library.
- Harden an existing application against XSS and HTML injection by tracing user-controlled inputs.
- Review and fix weak CSP configurations and insecure cookie handling.
- Verify that security patches actually close the vulnerability without introducing regressions.
Known limitations
Requires local Python 3 for the automated scanning script component. Cannot claim full exploitability from pattern matches alone without manual data-flow verification.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
Requires local Python 3 for the scanning script. Discovery phase is read-only; you must explicitly approve each patch ID before the agent edits code.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
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 3 months ago
Permissions
No special permissions declared or detected