security

Harden code against injection, traversal, process, and secret-handling risks.

47|11|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/styrene-lab/omegon --skill security-styrene-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/styrene-lab/omegon/tree/main/skills/security
Command: npx skills add https://github.com/styrene-lab/omegon --skill security-styrene-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent common security mistakes during implementation and review, reducing the risk of injection, traversal, secret leakage, and unsafe process handling.

Core Features & Use Cases

  • Input Escaping: Escape user-controlled values correctly for HTML, JavaScript, SQL, URLs, and shell-adjacent contexts.
  • Path Safety: Validate resolved paths so file access stays inside the intended root and cannot escape through traversal or symlinks.
  • Process and Secret Hygiene: Spawn child processes safely with argument arrays and timeouts, avoid inherited terminal I/O, and keep secrets out of source code and logs.

Quick Start

Review this codebase for security issues and apply the checklist to harden input handling, path validation, process spawning, and secret management.

Frequently Asked Questions about security

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

FAQPage Schema
How do I prevent path traversal attacks when handling file uploads?

Prevent path traversal by validating resolved file paths to ensure access stays root-bound, blocking escape attempts through directory traversal sequences or symlinks. This stops unauthorized file access outside intended directories.

What is the safest way to spawn child processes in a CLI application?

Safely spawn child processes by using argument arrays instead of shell strings, enforcing execution timeouts, and avoiding inherited terminal I/O to prevent command injection and hanging.

How do I escape user input correctly for HTML, JavaScript, and SQL contexts?

Escape user-controlled values by applying context-appropriate encoding for HTML, JavaScript, SQL, and URLs to prevent injection attacks across web and systems code.

Does this security review approach work for both web and systems code?

Yes, this security review approach applies to implementation and review work across web, CLI, TUI, and systems code where untrusted input, file paths, subprocesses, and credentials must be controlled.

How to manage secrets and prevent credential leakage in source code?

Manage secrets by keeping credentials out of source code and logs, enforcing strict secret hygiene to prevent accidental leakage during implementation and deployment.