sast-xss

Detect Cross-Site Scripting vulnerabilities by tracing user input through rendering sinks.

1.3k|61|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/utkusen/sast-skills --skill sast-xss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sast-xss
Source: https://github.com/utkusen/sast-skills/tree/main/sast-files/.agents/skills/sast-xss
Command: npx skills add https://github.com/utkusen/sast-skills --skill sast-xss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect Cross-Site Scripting vulnerabilities across codebases by tracing user-controlled input through rendering sinks.

Core Features & Use Cases

  • Three-phase XSS workflow (recon, batched verify, merge) to locate and validate vulnerabilities.
  • Requires sast/architecture.md to map sinks and data flows; outputs to sast/xss-results.md.
  • Useful for codebases with server-side rendering, client-side templates, and dynamic DOM updates to identify risky patterns.

Quick Start

Run the XSS detection workflow against your project to surface sink sites and generate a consolidated xss-results.md.

Frequently Asked Questions about sast-xss

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

FAQPage Schema
How do I find XSS vulnerabilities in a codebase with server-side rendering and dynamic DOM updates?

To find XSS vulnerabilities, this Skill traces unescaped user input through server-side template sinks, client-side DOM sinks, and JavaScript execution paths, generating a unified report of risky rendering patterns across the codebase.

What is taint-tracking for cross-site scripting and how does it identify unescaped user input?

Taint-tracking for cross-site scripting follows data flow from user-controlled inputs to rendering sinks. This Skill uses batched taint-tracking to verify if unescaped input reaches output paths, validating potential vulnerabilities across the codebase.

How do I run a static analysis workflow to detect XSS vulnerabilities step by step?

Run a static analysis workflow for XSS detection by executing a three-phase process: recon to locate sink sites, batched verify to taint-track input in parallel, and merge to produce a unified vulnerability report in sast/xss-results.md.

Do I need an architecture file to perform code analysis for XSS vulnerabilities?

Yes, code analysis for XSS vulnerabilities requires sast/architecture.md as architectural context to map sinks and data flows, enabling the Skill to accurately locate template sinks and trace user input paths before generating reports.

What's the best way to analyze large codebases for cross-site scripting without missing execution paths?

The best way to analyze large codebases for cross-site scripting is using batched parallel verification, which taint-tracks user input across JavaScript execution paths in parallel batches, ensuring comprehensive sink coverage and unified results.

What are the limitations of static code analysis for detecting XSS in client-side templates?

Static code analysis for XSS in client-side templates requires architectural context to map data flows and may need manual review of dynamically generated DOM updates, as automated taint-tracking focuses on identified sink sites and execution paths.