security-defensive

Audit code, configurations, and deployments for security best practices.

4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/rbaumier/skills --skill security-defensive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-defensive
Source: https://github.com/rbaumier/skills/tree/main/security-defensive
Command: npx skills add https://github.com/rbaumier/skills --skill security-defensive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams embed security into the software lifecycle, reducing the risk of insecure code, misconfigurations, and weak authentication by codifying robust defensive rules and practices.

Core Features & Use Cases

  • Comprehensive security guidelines: Covers input validation, authentication, authorization, CSRF, rate limiting, secrets management, and secure logging aligned with OWASP Top 10.
  • Pre-deployment hardening: Provides a structured checklist and patterns to harden apps before release, including secure cookie usage, CSP, and strict CORS policies.
  • Threat modeling and reviews: Enables systematic review of server and client code, APIs, and infrastructure to surface prototype pollution, RCE, SSRF, IDOR, and data leakage risks.
  • Use Case: A security engineer uses this Skill to perform an in-depth security review of a REST API, identifies a missing CSRF token in state-changing endpoints, and prescribes fixes.

Quick Start

Analyze a codebase to identify security gaps, prioritize remediation, and generate a concrete improvement plan.

Frequently Asked Questions about security-defensive

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

FAQPage Schema
How do I audit my codebase for OWASP Top 10 vulnerabilities?

To audit code for OWASP Top 10 vulnerabilities, analyze server and client code, APIs, and infrastructure to surface risks like prototype pollution, RCE, SSRF, and IDOR. This enforces strict schema validation and structured audit logging to identify security gaps.

What is the best way to harden a REST API before deployment?

The best way to harden a REST API before deployment is applying a structured checklist that enforces secure cookie usage, CSP, strict CORS policies, and TLS. This ensures robust authentication, authorization, and CSRF protection on state-changing endpoints.

How does input validation prevent security risks in microservices?

Input validation prevents security risks in microservices by enforcing strict schema validation across web services and APIs. This defensive practice stops malicious payloads from exploiting weak authentication, poor token handling, or insecure configurations.

Can I use this for threat modeling and security reviews of web services?

Yes, you can use this for threat modeling and security reviews of web services. It systematically reviews server and client code to surface data leakage risks, address CSRF, and prescribe concrete fixes for identified authentication or authorization gaps.

Why do I need strict schema validation and RBAC for software security?

You need strict schema validation and RBAC for software security because they enforce robust defensive rules against unauthorized access and malicious inputs. Combined with secure token handling and structured audit logging, they drive pre-deployment hardening and reduce data leakage risks.

Does this security review cover secrets management and infrastructure hygiene?

Yes, this security review covers secrets management and infrastructure hygiene. It audits code, configurations, and deployments to enforce TLS, CSP, and structured audit logging, ensuring comprehensive protection aligned with OWASP best practices.