perseus-client

Detect and remediate DOM XSS, prototype pollution, and SSR vulnerabilities in React, Vue, Angular, and Next.js codebases.

66|14|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kaivyy/perseus --skill perseus-client
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perseus-client
Source: https://github.com/kaivyy/perseus/tree/main/skills/perseus/specialists/client
Command: npx skills add https://github.com/kaivyy/perseus --skill perseus-client

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modern web applications increasingly rely on client-side logic across React, Vue, Angular, and SSR frameworks, yet detecting DOM XSS, template issues, and prototype pollution in the browser context remains error-prone and often overlooked.

Core Features & Use Cases

  • Deep client-side security analysis across popular frameworks (React, Vue, Angular, Next.js, Nuxt) focusing on DOM XSS, prototype pollution, and SSR risks.
  • Framework-specific pattern detection for risky bindings, dynamic components, and unsafe HTML injections with actionable remediation guidance.
  • Use Case: Before deploying a SPA, run the client-side specialist to surface vulnerabilities, prioritize fixes, and verify mitigations in a single pass.

Quick Start

Run the client-side specialist on your codebase to begin the automated security analysis.

Frequently Asked Questions about perseus-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find DOM XSS vulnerabilities in React and Vue applications?

Detecting DOM XSS vulnerabilities in React and Vue involves performing automated client-side security analysis to identify unsafe bindings and risky HTML rendering, then applying the provided actionable remediation guidance to fix the issues.

What is prototype pollution and how does it affect client-side security?

Prototype pollution is a client-side vulnerability where attackers modify JavaScript object prototypes, affecting client-side security by altering application logic. Automated analysis detects these risks across modern frameworks like Angular and Vue.

Does client-side security analysis work with Next.js and Nuxt.js SSR architectures?

Yes, client-side security analysis works with Next.js and Nuxt.js SSR architectures. The analysis specifically targets SSR risks and data leakage across these frameworks alongside standard single-page application logic.

How do I scan my codebase for unsafe HTML injections before deploying a SPA?

To scan your codebase for unsafe HTML injections before deploying a SPA, run an automated client-side security specialist to surface vulnerabilities, prioritize fixes by risk level, and verify mitigations in a single pass.

What is the best way to detect risky dynamic components in Angular?

The best way to detect risky dynamic components in Angular is to use framework-specific pattern detection during an automated security scan, which identifies unsafe bindings and dynamic component risks while offering actionable remediation guidance.

Why does my automated vulnerability analysis overlook framework-specific template issues?

Automated vulnerability analysis might overlook framework-specific template issues if it lacks dedicated pattern detection for modern frameworks. Specialized client-side analysis resolves this by mapping unsafe bindings and dynamic components directly to React, Vue, and Angular rules.