security-review

Guide security reviews with OWASP Top 10, threat modeling, and secure coding checklists.

3|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/doancan/mags --skill security-review-doancan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/doancan/mags/tree/main/skills/security-review
Command: npx skills add https://github.com/doancan/mags --skill security-review-doancan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured guidance for security reviews throughout the software lifecycle, helping teams identify threats, enforce secure design, and reduce risk.

Core Features & Use Cases

  • OWASP Top 10 checklist and mitigations for common categories.
  • Threat modeling guidance with data-flow diagrams and STRIDE analysis.
  • Secure coding practices, risk-based design reviews, and security checklists.
  • Practical processes for integrating security reviews into design, development, and deployment.

Quick Start

Trigger the security-review guidance to perform a rapid, risk-based security assessment for your project.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I perform a structured security review for my software project?

A structured security review applies threat modeling, secure coding practices, and OWASP Top 10 checklists across design, development, and deployment to identify and mitigate software project risks.

What is STRIDE analysis in threat modeling?

STRIDE analysis in threat modeling identifies software security threats by categorizing risks into Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege across data flows.

How do I check my application for OWASP Top 10 vulnerabilities?

Check OWASP Top 10 vulnerabilities by applying a structured security checklist that verifies secure coding practices and mitigations for common web application risk categories during development.

When do I need threat modeling documentation in the software lifecycle?

Threat modeling documentation is needed during software design, development, and deployment to enforce secure design checklists, map data flows, and provide actionable security recommendations for risk assessment.

Can I integrate secure coding practices into my existing development workflows?

Secure coding practices integrate into existing development workflows through risk-based design reviews and security checklists applied systematically across software design, development, and deployment phases.