security

Identify and mitigate security risks in web applications using OWASP guidelines.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pqem/agent-automatizado --skill security-pqem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/pqem/agent-automatizado/tree/main/templates/skills/tech/security
Command: npx skills add https://github.com/pqem/agent-automatizado --skill security-pqem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, practical framework to implement security best practices based on OWASP guidelines, helping teams reduce vulnerabilities and misconfigurations across software projects.

Core Features & Use Cases

  • OWASP Top 10 guidance and defensive checks for web apps and APIs.
  • Authentication, authorization, and secrets management patterns with concrete examples.
  • Secure headers, input validation, dependency auditing, and secure configuration guidance for reliable deployments.
  • Use cases span web services, microservices, and serverless functions requiring robust security guardrails.

Quick Start

Install and apply OWASP-aligned practices in your project by identifying sensitive entry points, enabling strong authentication, validating inputs, and configuring secure defaults.

Frequently Asked Questions about security

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

FAQPage Schema
How do I implement OWASP Top 10 security checks in my web application?

OWASP security checks identify and mitigate vulnerabilities by applying defensive validations and guardrails across code and configurations. This framework provides concrete patterns for authentication, input validation, and secure headers to reduce application risks.

What is the best way to manage secrets and configure secure defaults for microservices?

Secrets management and secure configuration require applying concrete technical practices that protect sensitive entry points. This approach implements authentication patterns and dependency auditing to ensure reliable deployments across web services and serverless functions.

How does input validation and secure headers prevent API security risks?

Input validation and secure headers mitigate API security risks by enforcing strict data boundaries and protective HTTP responses. Implementing these OWASP-aligned guardrails prevents misconfigurations and blocks common injection attacks targeting web services.

Can I apply these authentication and authorization patterns to serverless functions?

Authentication and authorization patterns apply directly to serverless functions requiring robust security guardrails. The framework supports implementing strong access controls and secrets management across microservices and web applications without architectural limitations.

Why do I need dependency auditing for secure software deployments?

Dependency auditing is needed for secure deployments because it identifies vulnerable components within your project's external libraries. Applying OWASP guidelines ensures dependencies are validated against known risks before reaching production environments.

When should I not use manual security configurations instead of a structured framework?

Manual security configurations should be avoided when deploying complex web applications or APIs with multiple sensitive entry points. A structured OWASP-aligned framework systematically applies validations and secure defaults that manual processes often miss.