web-security

Review web applications for CSRF, XSS, CSP, CORS, and OAuth 2.1 security risks.

2|1|Updated Jun 30, 2019
One-click install
npx skills add https://github.com/tgautier/dotfiles --skill web-security-tgautier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-security
Source: https://github.com/tgautier/dotfiles/tree/main/claude/skills/web-security
Command: npx skills add https://github.com/tgautier/dotfiles --skill web-security-tgautier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser-facing and API security guidance for production web applications, helping teams design secure architectures and avoid common web vulnerabilities.

Core Features & Use Cases

  • Threat modeling and defense-in-depth guidance covering CSRF, XSS, CSP, cookie security, CORS, session management, and authentication
  • JWT security, OAuth 2.1 considerations, PKCE requirements, token revocation and rotation patterns
  • Security headers, CSP configuration, input validation, dependency scanning, and supply-chain considerations
  • Use cases include implementing auth, reviewing security posture, configuring CORS/CSP/cookies, or hardening endpoints against browser-based attacks

Quick Start

Run an OWASP-aligned security review across browser and API endpoints to harden configurations.

Frequently Asked Questions about web-security

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

FAQPage Schema
How do I configure Content Security Policy headers to prevent XSS in my web app?

Configuring CSP headers prevents XSS by restricting approved script execution sources. This Skill provides defense-in-depth guidance for CSP configuration, input validation, and browser security hardening aligned with OWASP cheat sheets.

What is the best way to implement OAuth 2.1 and JWT token rotation securely?

Implementing OAuth 2.1 and JWT token rotation securely requires PKCE for all clients and proper token lifetimes. This Skill guides authentication patterns, token revocation, and session management aligned with RFC 9700 guidance.

How do I harden API endpoints against the OWASP API Security Top 10 vulnerabilities?

Hardening API endpoints against OWASP API Security Top 10 requires addressing CSRF, CORS, and SSRF risks. This Skill applies threat modeling to review security posture and configure browser-facing protections for production web applications.

Can I use this to review cookie security and CORS configurations for my API?

Yes, you can use this to review cookie security and CORS configurations. It provides cross-cutting web security guidance for production web apps, covering cookie attributes, CORS policies, and security headers across Rust and TypeScript stacks.

Why do I need PKCE for all OAuth clients and how does it prevent token theft?

PKCE is required for all OAuth clients to prevent authorization code interception and token theft. This Skill aligns with OAuth 2.1 considerations, enforcing PKCE requirements and best-practice token rotation patterns for secure authentication.

What are the limitations of relying only on input validation for web application security?

Relying only on input validation leaves threats like CSRF, XSS, and SSRF unmitigated. This Skill applies defense-in-depth, combining CSP configuration, dependency scanning, security headers, and session management to harden production web applications.