security-and-hardening

Harden software by applying threat modeling and boundary validation controls.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hodinhtuankiet/screening-resume-recruitment --skill security-and-hardening-hodinhtuankiet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-and-hardening
Source: https://github.com/hodinhtuankiet/screening-resume-recruitment/tree/main/.claude/skills/security-and-hardening
Command: npx skills add https://github.com/hodinhtuankiet/screening-resume-recruitment --skill security-and-hardening-hodinhtuankiet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

Core Features & Use Cases

  • Threat modeling-guided security: maps trust boundaries, inventories assets, and applies STRIDE across boundaries to identify attack surfaces.
  • Boundary-focused controls: enforces input validation, parameterized queries, secure data handling, proper encoding, and strict cryptographic practices.
  • LLM and AI safety: treats model outputs as untrusted, defends against prompt injection, prevents data leakage, and constrains tool capabilities.
  • Secure development guidance: encourages abuse-case thinking, security headers, session security, and secure secret management.

Quick Start

Perform a quick threat model for the feature, enumerate trust boundaries and assets, then implement three concrete hardening steps at boundary points.

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 code against vulnerabilities when handling untrusted user input?

Harden code against vulnerabilities by treating every input as untrusted and implementing robust controls at system boundaries. This involves enforcing input validation, parameterized queries, and secure data handling to protect web apps, APIs, and external integrations.

What is threat modeling and how does it identify attack surfaces?

Threat modeling identifies attack surfaces by mapping trust boundaries, inventorying assets, and applying STRIDE across boundaries. This process systematically exposes security risks in software features before implementation begins.

How do I secure LLM and AI integrations against prompt injection attacks?

Secure LLM and AI integrations by treating model outputs as untrusted data. Defend against prompt injection, prevent data leakage, and strictly constrain tool capabilities to ensure safe AI usage within your application boundaries.

Does this security framework align with OWASP principles for web apps and APIs?

This security framework aligns with OWASP principles and secure-by-design guidelines. It enforces boundary-focused controls, proper encoding, strict cryptographic practices, and secure secret management across web apps, APIs, and services.

What's the best way to start implementing secure authentication and session management?

Start implementing secure authentication by performing a quick threat model for the feature, enumerating trust boundaries and assets, then applying three concrete hardening steps at boundary points like session validation.

When do I need strict boundary validation for external service integrations?

Strict boundary validation is needed whenever building features that interact with third-party services or external integrations. It ensures untrusted data is sanitized at entry points, preventing vulnerabilities from propagating into internal systems.