threat-model-generation

Generate a STRIDE-based threat model with threat-model.md and security-config.json.

101|10|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/Factory-AI/factory-plugins --skill threat-model-generation-factory-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: threat-model-generation
Source: https://github.com/Factory-AI/factory-plugins/tree/main/plugins/security-engineer/skills/threat-model-generation
Command: npx skills add https://github.com/Factory-AI/factory-plugins --skill threat-model-generation-factory-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling helps security teams and engineers identify STRIDE-based threats early by modeling a repository’s architecture, data flows, and trust boundaries to produce actionable mitigations.

Core Features & Use Cases

  • STRIDE-based threat modeling for codebases and deployments
  • Trust boundary mapping and data-flow analysis to identify critical assets
  • Deliverables include a comprehensive threat model document and a configuration for security tooling
  • Use Case: When starting a new project, after major architectural changes, or as part of a security audit

Quick Start

Analyze your repository to generate a STRIDE threat model and its supporting documentation.

Frequently Asked Questions about threat-model-generation

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

FAQPage Schema
How do I generate a STRIDE threat model for my repository?▼

Generate a STRIDE threat model by analyzing the repository structure, mapping trust boundaries, cataloging assets, and applying the STRIDE methodology to document attack surfaces and mitigations.

What is STRIDE-based threat modeling in software architecture?▼

STRIDE threat modeling is a security analysis technique that identifies spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege threats across a repository's architecture and trust boundaries.

When do I need to perform threat modeling on a codebase?▼

Perform threat modeling on a codebase when starting a new project, after major architectural changes, or during periodic security audits to identify emerging threats and document updated mitigations.

What files are produced when documenting a repository security analysis?▼

Documenting a repository security analysis produces a threat-model.md file detailing threats and mitigations, alongside a security-config.json file for configuring supporting security tooling.

Does threat modeling work for existing repositories or only new project security setup?▼

Threat modeling works for both new project security setup and existing repositories, supporting initial architecture analysis, major changes, and periodic security audits to document attack surfaces.