security-and-hardening

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

Enforce security best practices for web application code paths.

Updated Aug 23, 2026

Search Tags:#authorization #security #authentication #owasp #input-validation #hardening #secure-coding

Ready to run

npx skills add https://github.com/Coldaine/agent-skills-vscode --skill security-and-hardening-coldaine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-and-hardening
Source: https://github.com/Coldaine/agent-skills-vscode/tree/main/skills/security-and-hardening
Command: npx skills add https://github.com/Coldaine/agent-skills-vscode --skill security-and-hardening-coldaine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security-first development practices for web applications. Treat every external input as hostile, every secret as sacred, and every authorization check as mandatory. Security isn't a phase — it's a constraint on every line of code that touches user data, authentication, or external systems.

Core Features & Use Cases

Establishes boundary validation and strict input handling to prevent common vulnerabilities.
Enforces secure session management, headers, and cookie policies to protect data in transit and at rest.
Provides guidance on secure defaults, OWASP top-10 prevention, and risk-based decision making for external integrations.

Quick Start

Secure every code path by auditing inputs, enforcing parameterized queries, and applying strict security headers.

Frequently Asked Questions about security-and-hardening

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

FAQPage Schema

How do I enforce secure coding practices to prevent OWASP top-10 vulnerabilities in web applications?▼

To prevent OWASP top-10 vulnerabilities, enforce boundary input validation, parameterized queries, secure cookies, and strict security headers like CSP and HSTS across all web application code paths handling user data and external integrations.

What is the best way to implement strict input validation and boundary security for API routes?▼

The best way to implement strict input validation is by treating every external input as hostile and enforcing validation at the boundary using explicit 'Never' and 'Always' rules for parameterized queries before data reaches authentication or storage layers.

How do I secure authentication and authorization checks across my application's code paths?▼

Secure authentication and authorization by enforcing mandatory access controls, secure session management, and strict cookie policies for every code path touching user data, treating every authorization check as mandatory and every secret as sacred.

Does this security hardening approach work for both frontend and backend API integration code?▼

Yes, security hardening works for any web application development project from API routes to frontend, covering input validation, authentication, data protection, secure communications, and dependency hygiene across all external integration points.

How do I apply secure defaults for secret management and security headers in web development?▼

Apply secure defaults by enforcing strict boundary rules: use secure cookies, implement CSP and HSTS headers, and manage secrets as sacred constraints on every line of code touching authentication or external systems.

What are the limitations of boundary validation when handling external integrations and dependency hygiene?▼

Boundary validation limitations arise when external integrations introduce risk-based decisions beyond your control; while it enforces secure defaults and treats external input as hostile, dependency hygiene requires continuous monitoring and risk assessment of external systems.