web-security

Enforce web security policies for input validation, CSP, and secure cookies.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/ddoman90/claude-code-intro --skill web-security-ddoman90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-security
Source: https://github.com/ddoman90/claude-code-intro/tree/main/.claude/skills/web-security
Command: npx skills add https://github.com/ddoman90/claude-code-intro --skill web-security-ddoman90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce web security as a core requirement so teams consistently build resilient, attack-aware applications, reducing vulnerabilities caused by untrusted input and unsafe configurations.

Core Features & Use Cases

  • Never trust user input and enforce validation at all boundaries.
  • Always implement proper authentication, authorization, and secure cookie handling.
  • Apply Content Security Policy (CSP) and secure defaults to minimize attack surfaces across web apps.
  • Use Case: For a new web app, establish a secure-by-default baseline and perform threat modeling to prevent XSS, CSRF, and data leakage.

Quick Start

Review your app against input validation, CSP, and secure cookie policies, and document any high-risk items.

Frequently Asked Questions about web-security

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

FAQPage Schema
How do I prevent XSS and CSRF vulnerabilities in my web application?

Prevent XSS and CSRF by enforcing strict input validation at all boundaries and implementing Content Security Policy headers. This approach stops untrusted input from executing malicious scripts and blocks unauthorized cross-site requests.

What is the best way to enforce secure coding practices for user input validation?

Enforce secure coding by never trusting user input and applying strict validation at all application boundaries. This prevents malicious data from entering your system and causing data leakage or injection attacks.

How do I configure Content Security Policy and secure cookies for new web apps?

Configure CSP and secure cookies by applying secure defaults that minimize the application attack surface. Proper cookie handling and CSP headers restrict external resource loading and protect session integrity.

Do I need threat modeling to establish a secure-by-default baseline for my web app?

Threat modeling is needed to establish a secure-by-default baseline because it helps identify potential XSS, CSRF, and data leakage risks across APIs and third-party integrations before deployment.

Why does my web application still have data leakage issues despite authentication?

Data leakage persists despite authentication when secure cookie handling and authorization policies are incomplete. Enforcing proper input validation and audit logging across APIs and third-party integrations closes these security gaps.