security

Enforce OWASP security patterns, secrets management, and automated security testing.

31|1|Updated Feb 12, 2026

Search Tags:#security #owasp #secrets management #dependency audit #vulnerability scanning #code hardening

Ready to run

npx skills add https://github.com/Pouzor/pilotarr --skill security-pouzor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/Pouzor/pilotarr/tree/main/.claude/skills/security
Command: npx skills add https://github.com/Pouzor/pilotarr --skill security-pouzor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill establishes and enforces robust security practices across your projects, preventing common vulnerabilities and protecting sensitive information.

Core Features & Use Cases

Secret Management: Guides on securely handling API keys, passwords, and environment variables.
Dependency Auditing: Integrates tools to scan for vulnerable libraries.
Code Analysis: Provides checks for common security flaws like SQL injection and XSS.
Use Case: Ensure your new feature branch adheres to all security standards before merging by running pre-commit hooks and a GitHub Actions workflow that scans for secrets and dependency vulnerabilities.

Quick Start

Run the security skill to enforce best practices for handling secrets and dependencies in your project.

Frequently Asked Questions about security

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

FAQPage Schema

How do I prevent secrets like API keys from being committed to my repository?▼

Secrets management is enforced by integrating pre-commit hooks and GitHub Actions workflows that scan your codebase. This prevents sensitive API keys, passwords, and environment variables from being accidentally pushed to your repository.

How do I scan my project for vulnerable dependencies and libraries?▼

You can scan for vulnerable dependencies by running automated security testing integrated into your workflow. This dependency auditing process identifies known vulnerabilities in your project libraries before they reach production.

What is the best way to enforce OWASP security patterns for SQL injection and XSS?▼

Enforcing OWASP security patterns involves integrating code analysis checks that identify and mitigate common flaws like SQL injection and XSS. These checks validate inputs and ensure secure authentication and data handling principles are applied.

Can I use GitHub Actions workflows to automate vulnerability scanning before merging code?▼

Yes, you can automate vulnerability scanning before merging by integrating GitHub Actions workflows. These workflows run alongside pre-commit hooks to scan for secrets, audit dependencies, and verify adherence to security standards.

Does this automated security testing require specific secure coding principles for authentication?▼

Yes, the automated security testing requires adherence to secure coding principles for authentication, authorization, and data handling. This ensures your codebase effectively mitigates risks like SQL injection and cross-site scripting.

What are the limitations of using pre-commit hooks for code hardening and security checks?▼

Pre-commit hooks for code hardening only enforce security checks locally before code is pushed. They must be paired with remote GitHub Actions workflows to ensure vulnerabilities and secrets are blocked if a developer bypasses local hooks.