security-and-hardening

Name: security-and-hardening
Availability: InStock
Author: kevindree

Harden web application code against OWASP security vulnerabilities and unsafe external input.

Updated May 3, 2026

Search Tags:#authorization #security #authentication #input validation #owasp #secrets management #hardening

Ready to run

npx skills add https://github.com/kevindree/geehoo-gateway --skill security-and-hardening-kevindree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-and-hardening
Source: https://github.com/kevindree/geehoo-gateway/tree/main/.github/skills/security-and-hardening
Command: npx skills add https://github.com/kevindree/geehoo-gateway --skill security-and-hardening-kevindree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers harden applications against common security flaws by turning security best practices into concrete implementation guidance for everyday web development.

Core Features & Use Cases

Input Defense: Validate untrusted data at the boundary to reduce injection, cross-site scripting, and unsafe parsing risks.
Authentication and Access Control: Strengthen login, session, authorization, and role-based permission checks for protected endpoints.
Data and Integration Safety: Protect secrets, secure headers, CORS, cookies, external API calls, file uploads, and other high-risk integration points.
Use Case: A team shipping an API gateway can use this Skill to review request handling, upstream integrations, and configuration choices before release.

Quick Start

Use this skill to review your application for unvalidated input, missing authorization, secret leakage, weak session handling, insecure CORS, and other OWASP risks, then apply the recommended hardening changes.

Frequently Asked Questions about security-and-hardening

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

FAQPage Schema

How do I harden web application code against OWASP vulnerabilities like injection and XSS?▼

Application hardening requires enforcing input validation at boundaries and applying OWASP-aligned defenses against injection, XSS, and access control failures. It involves strengthening authentication, session handling, and role-based authorization checks across protected endpoints.

What is the best way to secure API endpoints and third-party integrations in production services?▼

Securing API endpoints requires implementing rate limiting, safe handling of external API calls, and strict CORS policies. You must protect secrets, enforce HTTPS, set secure headers, and audit dependencies to prevent sensitive data exposure during third-party integrations.

Does this security review cover file uploads, webhooks, and session management?▼

Yes, this security review covers file uploads, webhooks, and session management. It provides implementation guidance for securing these high-risk integration points, ensuring safe cookies, proper authorization, and protected data storage across web applications.

How do I validate untrusted data to prevent cross-site scripting and unsafe parsing risks?▼

Validating untrusted data requires enforcing strict input validation at system boundaries to reduce injection, cross-site scripting, and unsafe parsing risks. This boundary defense mechanism ensures external requests are sanitized before reaching application logic or storage layers.

What security headers and cookie settings do I need to protect sensitive data from exposure?▼

Protecting sensitive data requires enforcing HTTPS, configuring safe cookies, and applying appropriate security headers. These measures prevent unauthorized access and data leakage, working alongside secrets management and dependency auditing to harden application configurations.