security-and-hardening

Enforce input validation, output encoding, and secure secret management across the development lifecycle.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill security-and-hardening-kevinnft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-and-hardening
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/addyosmani/security-and-hardening
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill security-and-hardening-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hardens software by instilling security-first practices across the development lifecycle, reducing the risk of common vulnerabilities in input handling, authentication, data storage, and external integrations.

Core Features & Use Cases

  • Input validation at boundaries: enforce strict checks on all external data before processing.
  • Output encoding and sanitization: prevent injection attacks in UI rendering and APIs.
  • Secrets management and secure storage: avoid leaking API keys and credentials through proper storage and access controls.
  • Security headers and access controls: implement CSP, HSTS, and proper authentication/authorization checks.

Quick Start

Apply security-first guidelines in your codebase by validating all input, encoding outputs, enforcing authentication and authorization, and securely managing secrets.

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 my web application against common OWASP vulnerabilities?▼

To harden web applications against vulnerabilities, enforce strict input validation at boundaries, apply output encoding, and implement security headers like CSP and HSTS to reduce injection and cross-site risks.

What is the best way to prevent injection attacks in UI rendering and APIs?▼

Preventing injection attacks requires consistent output encoding and sanitization across UI rendering and APIs, ensuring external data is neutralized before it is executed or rendered by the application.

How do I securely manage API keys and credentials in my codebase?▼

Secure secrets management and secure storage prevent leaking API keys and credentials by enforcing proper storage mechanisms and access controls rather than hardcoding sensitive data in source code.

When do I need to enforce input validation at trust boundaries?▼

Input validation at trust boundaries is needed whenever external data enters processing, enforcing strict checks on all untrusted inputs before the application processes them to mitigate vulnerabilities.

Does this security-first approach apply across the entire software development lifecycle?▼

Security-first coding guidelines apply across the development lifecycle, covering input handling, authentication, data storage, and external integrations to systematically reduce software vulnerabilities.