Perform comprehensive security audits of frontend codebases to identify vulnerabilities, bad practices, and missing protections.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfrontend-securityExecute the skills CLI command in your project's root directory to begin installation:
Fetches frontend-security from schalkneethling/webdev-agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate frontend-security. Access via /frontend-security in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
25
total installs
25
this week
3
GitHub stars
0
upvotes
Run in your terminal
25
installs
25
this week
3
stars
Perform comprehensive security audits of frontend codebases to identify vulnerabilities, bad practices, and missing protections.
# React dangerous patterns
grep -rn "dangerouslySetInnerHTML" --include="*.jsx" --include="*.tsx" --include="*.js"
# Direct DOM manipulation
grep -rn "\.innerHTML\s*=" --include="*.js" --include="*.ts" --include="*.jsx" --include="*.tsx"
grep -rn "\.outerHTML\s*=" --include="*.js" --include="*.ts"
grep -rn "document\.write" --include="*.js" --include="*.ts"
# URL-based injection
grep -rn "location\.href\s*=" --include="*.js" --include="*.ts"
grep -rn "location\.replace" --include="*.js" --include="*.ts"
grep -rn "window\.open" --include="*.js" --include="*.ts"
# Eval and code execution
grep -rn "eval\s*(" --include="*.js" --include="*.ts"
grep -rn "new Function\s*(" --include="*.js" --include="*.ts"
grep -rn "setTimeout\s*(\s*['\"]" --include="*.js" --include="*.ts"
grep -rn "setInterval\s*(\s*['\"]" --include="*.js" --include="*.ts"
# Twig unescaped output
grep -rn "|raw" --include="*.twig" --include="*.html.twig"
grep -rn "{% autoescape false %}" --include="*.twig"
# Forms without CSRF tokens
grep -rn "<form" --include="*.html" --include="*.jsx" --include="*.tsx" --include="*.twig"
# State-changing requests without protection
grep -rn "fetch\s*(" --include="*.js" --include="*.ts" | grep -E "(POST|PUT|DELETE|PATCH)"
grep -rn "axios\.(post|put|delete|patch)" --include="*.js" --include="*.ts"
# localStorage/sessionStorage with sensitive data
grep -rn "localStorage\." --include="*.js" --include="*.ts"
grep -rn "sessionStorage\." --include="*.js" --include="*.ts"
# Hardcoded secrets
grep -rn "api[_-]?key\s*[:=]" --include="*.js" --include="*.ts" --include="*.env"
grep -rn "secret\s*[:=]" --include="*.js" --include="*.ts"
grep -rn "password\s*[:=]" --include="*.js" --include="*.ts"
Load these references based on findings:
references/xss-prevention.mdreferences/csrf-protection.mdreferences/dom-security.mdreferences/csp-configuration.mdreferences/input-validation.mdreferences/nodejs-npm-security.mdreferences/framework-patterns.mdreferences/file-upload-security.mdreferences/jwt-security.mdCRITICAL - Exploitable XSS, authentication bypass, secrets exposure HIGH - Missing CSRF protection, unsafe DOM manipulation, SQL injection vectors MEDIUM - Weak CSP, missing security headers, improper input validation LOW - Informational disclosure, deprecated functions, suboptimal practices
## Security Audit Report
### Summary
- Critical: X findings
- High: X findings
- Medium: X findings
- Low: X findings
### Critical Findings
#### [CRITICAL-001] Title
- **Location**: file:line
- **Pattern**: Code snippet
- **Risk**: Description of the vulnerability
- **Remediation**: How to fix
- **Reference**: OWASP link
### High Findings
[...]
For comprehensive guidance, consult these OWASP cheatsheets directly:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
github/awesome-copilot
code-yeongyu/oh-my-opencode
alirezarezvani/claude-skills
shadcn/improve
mblode/agent-skills
I recommend frontend-security for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added frontend-security from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: frontend-security is the kind of skill you can hand to a new teammate without a long onboarding doc.
frontend-security has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in frontend-security — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in frontend-security — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
frontend-security has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: frontend-security is focused, and the summary matches what you get after install.
Registry listing for frontend-security matched our evaluation — installs cleanly and behaves as described in the markdown.
frontend-security reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 40