security

Create and update STRIDE threat models in Markdown.

9|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/0xrafasec/ai-workflow --skill security-0xrafasec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/0xrafasec/ai-workflow/tree/main/skills/security
Command: npx skills add https://github.com/0xrafasec/ai-workflow --skill security-0xrafasec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation and revision of security threat models, reducing the complexity and time required to conduct thorough security reviews.

Core Features & Use Cases

  • Threat Model Creation: Develop STRIDE-style threat models with trust boundaries and attack surface analysis.
  • Security Review: Facilitate security reviews by gathering context and guiding through interviews.
  • Documentation: Outputs a structured docs/THREAT_MODEL.md file that can be reviewed and iterated upon.
  • Use Case: When starting a new project or reviewing the security posture of an existing one, use this Skill to automatically generate a threat model based on the system's architecture and codebase.

Quick Start

Generate a threat model for your project by running 'security'.

Frequently Asked Questions about security

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

FAQPage Schema
How do I generate a threat model for my software project?

To generate a threat model, run the 'security' command in your project directory. It automates STRIDE analysis, trust boundary mapping, and attack surface identification by interacting with your codebase and system documentation, outputting a structured Markdown file.

What is STRIDE analysis and how does it apply to threat modeling?

STRIDE analysis is a framework for identifying security threats like spoofing and tampering. This Skill applies it to your software architecture to map trust boundaries and attack surfaces, producing a comprehensive threat model document for review.

Can I use this threat modeling tool for an existing codebase?

Yes, you can use it for existing projects to review their security posture. The tool requires interaction with your current system documentation and codebase to effectively identify architectural vulnerabilities and generate an accurate threat model.

Do I need system documentation before creating a threat model?

Yes, system documentation is required to effectively map trust boundaries and identify attack surfaces. The tool analyzes your existing architecture documents and codebase to automate the creation of an accurate STRIDE-based threat model.

What is the best way to document a security review for a software architecture?

The best way is to automate the documentation using a structured threat model. This Skill generates a 'docs/THREAT_MODEL.md' file containing your STRIDE analysis, trust boundaries, and attack surface details, which can be iterated upon during reviews.