security-and-hardening

Enforce secure coding practices for authentication, authorization, and data handling.

2|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/huangzida/skills --skill security-and-hardening-huangzida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-and-hardening
Source: https://github.com/huangzida/skills/tree/main/security-and-hardening
Command: npx skills add https://github.com/huangzida/skills --skill security-and-hardening-huangzida

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

  • Three-Tier Boundary System: Always validate external input at the boundary, parameterize database queries, encode outputs, enforce HTTPS, set secure cookies, and run npm audit before releases.
  • OWASP Top 10 Prevention: Implement protections against common weaknesses such as injection, broken authentication, and misconfigurations with concrete patterns and checks.
  • Input Validation & Data Handling: Enforce strict input validation, proper output encoding, and safe handling of sensitive data, secrets, and tokens.
  • Secrets & Configuration Management: Avoid hard-coded keys; recommend environment-based secrets management, rotation, and minimal privilege design.

Quick Start

Integrate security-first guidelines from this Skill into your codebase and start applying input validation, secret management, and defensive coding practices immediately.

Frequently Asked Questions about security-and-hardening

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

FAQPage Schema
Does this security hardening approach work for external integrations and API data handling?

Security hardening applies across external integrations to guard systems from untrusted input. It enforces strict input validation, proper output encoding, and mandatory authorization checks for all data handling and external system interactions.

How do I prevent OWASP Top 10 vulnerabilities like injection and broken authentication in my web application?

Preventing OWASP Top 10 vulnerabilities requires enforcing secure coding practices across authentication, authorization, and data handling. Implement concrete protection patterns, parameterize database queries, and validate all external input at system boundaries.

What is the best way to handle secrets and configuration to avoid hard-coded keys?

Secrets management prevents hardcoded keys by recommending environment-based secrets management, rotation, and minimal privilege design. Treat every secret as sacred and avoid embedding sensitive tokens or configuration directly within your application codebase.

How do I validate external input and enforce safe data handling in web applications?

Input validation guards systems from untrusted input by enforcing strict validation at the boundary, proper output encoding, and safe handling of sensitive data. Treat every external input as hostile to prevent injection and broken authentication vulnerabilities.

What is the best way to integrate security hardening guardrails into a development workflow?

Security hardening integrates into development workflows by applying practical guardrails, threat modeling guidance, and validation patterns across every line of code touching user data. Run npm audit before releases and enforce secure cookies and HTTPS.

Does this security hardening approach work for external integrations and API data handling?

Security hardening applies across external integrations to guard systems from untrusted input. It enforces strict input validation, proper output encoding, and mandatory authorization checks for all data handling and external system interactions.