owasp-security

Name: owasp-security
Availability: InStock
Author: raphaelmans

Enforce OWASP Top 10 secure coding practices across code, APIs, and configurations.

Updated Feb 28, 2026

Search Tags:#authorization #authentication #owasp #threat-modeling #vulnerability-prevention #security-review #secure-coding

Ready to run

npx skills add https://github.com/raphaelmans/agent-skills --skill owasp-security-raphaelmans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: owasp-security
Source: https://github.com/raphaelmans/agent-skills/tree/main/owasp-security
Command: npx skills add https://github.com/raphaelmans/agent-skills --skill owasp-security-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents web application vulnerabilities by guiding secure coding practices aligned with the OWASP Top 10 across authentication, input handling, API security, and secure configuration.

Core Features & Use Cases

Provide an actionable checklist to implement OWASP Top 10 mitigations during development, reviews, and deployments.
Demonstrate secure patterns, threat-modeling guidance, and secure defaults to harden APIs and web apps.
Use Case: A development team audits a new API and applies recommended mitigations to prevent common vulnerabilities such as injection, broken access control, and misconfigurations.

Quick Start

Audit a codebase against OWASP Top 10 controls and implement the recommended fixes for authentication, input validation, and secure headers.

Frequently Asked Questions about owasp-security

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

FAQPage Schema

How do I audit my codebase against OWASP Top 10 secure coding practices?▼

To audit code against OWASP Top 10 secure coding practices, apply an actionable checklist covering authentication, input validation, API security, and secure configuration. This process identifies vulnerabilities like injection and broken access control to implement recommended mitigations.

What is threat modeling and how does it prevent broken access control in APIs?▼

Threat modeling prevents broken access control in APIs by analyzing security boundaries and enforcing robust authorization patterns. It provides guidance on secure defaults and session management to harden web applications against unauthorized access.

How do I implement secure defaults and dependency hygiene across release pipelines?▼

Implement secure defaults and dependency hygiene across release pipelines by applying OWASP-aligned guidance to secure configurations. This ensures robust session management, validates security headers, and prevents misconfigurations during deployment.

Can I use OWASP security guidelines to review authentication and data handling in web apps?▼

Yes, you can use OWASP security guidelines to review authentication and data handling in web apps. The guidelines enforce secure patterns for input validation, API security, and robust session management to prevent common vulnerabilities.

What's the best way to harden APIs and prevent injection vulnerabilities during development?▼

The best way to harden APIs and prevent injection vulnerabilities during development is applying OWASP Top 10 mitigations. This involves enforcing strict input validation, secure coding patterns, and secure configuration reviews across the application.

Does this OWASP security approach apply to security configuration review and security headers?▼

Yes, this OWASP security approach applies to security configuration review and security headers. It enforces secure defaults and dependency hygiene across release pipelines, ensuring applications are hardened against misconfigurations and common web threats.