skill-security

Identify and mitigate OWASP Top 10 security risks in PHP applications.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/claudioborja/biblioteca --skill skill-security-claudioborja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-security
Source: https://github.com/claudioborja/biblioteca/tree/main/.agents/skills/skill-security
Command: npx skills add https://github.com/claudioborja/biblioteca --skill skill-security-claudioborja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive, battle-tested framework for securing PHP applications, addressing authentication, authorization, input validation, output encoding, and secure deployment practices to minimize OWASP risks.

Core Features & Use Cases

  • Defense in depth: combine input validation, parameterized queries, proper output encoding, and strict permission checks across all layers.
  • OWASP Top 10 prevention references: practical guidance for IDOR, SQL injection, CSRF, XSS, and insecure design patterns tailored to pure PHP stacks.
  • Security infrastructure: CSP headers, secure cookies, hashed tokens, safe redirects, logging, and a complete workflow checklist for incident response and dependency auditing.

Quick Start

Integrate strong password hashing, prepared statements, CSP headers, strict session handling, and a comprehensive security checklist to harden a pure PHP application.

Frequently Asked Questions about skill-security

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

FAQPage Schema
How do I prevent OWASP Top 10 vulnerabilities like SQL injection and CSRF in a PHP application?

To prevent OWASP Top 10 vulnerabilities in a PHP application, apply defense-in-depth using prepared statements for all database access, hash_equals for token comparisons, and strict input validation. This framework enforces these production-grade security controls.

How does defense-in-depth work for securing PHP authentication and authorization?

Defense-in-depth for PHP authentication secures systems by combining strong password hashing, strict session handling, parameterized queries, and strict permission checks across all layers to prevent IDOR and unauthorized access.

What is the best way to implement secure PHP sessions with CSP headers and safe cookies?

The best way to implement secure PHP sessions is by setting secure cookies, applying Content Security Policy headers, and enforcing strict session handling. This approach hardens the application against XSS and session hijacking.

Does pure PHP require prepared statements and output encoding to mitigate XSS and SQL injection risks?

Yes, pure PHP requires prepared statements for all database access and proper output encoding to mitigate XSS and SQL injection. This ensures user input is never executed as code or query logic.

How do I set up an incident response and security logging workflow for PHP systems?

To set up an incident response and security logging workflow for PHP systems, integrate comprehensive logging and follow a structured security checklist. This framework provides the necessary workflow-driven checklist for auditing dependencies and responding to incidents.

Why should I use hash_equals for token comparisons and secure redirects in PHP?

You should use hash_equals for token comparisons in PHP to prevent timing attacks, and implement safe redirects to stop open redirect vulnerabilities. These practices enforce secure authorization and output handling.