security-and-hardening

Applies OWASP-aligned security controls and threat modeling to software systems.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/MinhDuyDEV/mdpi --skill security-and-hardening-minhduydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-and-hardening
Source: https://github.com/MinhDuyDEV/mdpi/tree/main/.pi/skills/security-and-hardening
Command: npx skills add https://github.com/MinhDuyDEV/mdpi --skill security-and-hardening-minhduydev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers prevent security vulnerabilities by applying security-first practices across authentication, authorization, input handling, secrets management, dependency auditing, and production hardening.

Core Features & Use Cases

  • Threat Modeling and Secure Design: Guides teams through trust boundary analysis, abuse cases, STRIDE assessment, and security constraints before implementation.
  • Application Security Hardening: Covers OWASP Top 10 prevention patterns, secure authentication, validation, encryption, rate limiting, and dependency security reviews.
  • AI Security Practices: Provides guidance for protecting LLM-powered applications from prompt injection, unsafe outputs, excessive agency, and data exposure.
  • Use Case: A developer preparing an API for production can use this Skill to identify insecure endpoints, strengthen validation, configure secure defaults, and verify security controls.

Quick Start

Use the security-and-hardening skill to review my application architecture and identify security risks with recommended fixes.

Frequently Asked Questions about security-and-hardening

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

FAQPage Schema
How do I review my application architecture for security risks and identify fixes?

Security hardening prevents vulnerabilities by applying secure development practices across authentication, authorization, and input handling. It guides teams through threat modeling, OWASP Top 10 prevention patterns, and dependency audits to reduce attack surfaces and protect sensitive data.

What is threat modeling and when do I need it for secure coding?

Threat modeling is a structured analysis of trust boundaries and abuse cases needed before software implementation. You need it during the secure design phase to define security constraints, perform STRIDE assessments, and proactively reduce the application's attack surface.

How do I protect my LLM-powered application from prompt injection and data exposure?

Protecting LLM-powered applications from prompt injection requires applying AI security practices that mitigate unsafe outputs and excessive agency. Implementing strict validation checks, secure defaults, and data exposure controls reduces the risk of malicious inputs manipulating model behavior.

What's the best way to harden an API for production and prevent OWASP Top 10 vulnerabilities?

The best way to harden an API for production is by applying OWASP-aligned controls, secure authentication, and rate limiting. Identifying insecure endpoints, strengthening input validation, configuring secure defaults, and verifying security controls prevent OWASP Top 10 vulnerabilities.

Can I use this approach to audit dependencies and manage secrets in my software systems?

Yes, you can use secure development practices to audit dependencies and manage secrets in software systems. Dependency security reviews and secrets management ensure hardening techniques reduce attack surfaces and protect sensitive data across your application infrastructure.