threat_modeling

Produce a STRIDE-style threat model with assets and trust boundaries in threat_model.md.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/4tie/fortiesr --skill threat-modeling-4tie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat_modeling
Source: https://github.com/4tie/fortiesr/tree/main/.local/skills/threat_modeling
Command: npx skills add https://github.com/4tie/fortiesr --skill threat-modeling-4tie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a project's architecture into a concise security reference that helps teams spot assets, trust boundaries, and likely threats before launch.

Core Features & Use Cases

  • Produces a project-level threat model for new features, architecture changes, and pre-deploy reviews.
  • Identifies assets, trust boundaries, and STRIDE-style risks that matter to engineers and reviewers.
  • Captures reusable scan anchors and security guarantees in a format another agent can use for future analysis.

Quick Start

Use the threat modeling skill to review the repository architecture and write a concise threat_model.md summary in the project root.

Frequently Asked Questions about threat_modeling

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

FAQPage Schema
How do I create a threat model for a new software feature?

A threat model maps security risks by analyzing your software architecture to identify assets, trust boundaries, and STRIDE-style risks. This skill produces a structured threat_model.md file to help teams spot vulnerabilities before deployment.

What's the best way to perform a security review before deployment?

Perform a pre-deploy security review by mapping your attack surface with a structured threat model. This skill generates a concise security reference covering assets, trust boundaries, and required security guarantees for engineering teams.

How do I apply STRIDE analysis to my project's architecture?

Apply STRIDE analysis by reviewing your architecture for new features, storage, or third-party integrations. This skill captures STRIDE-style risks, scan anchors, and security guarantees in a reusable threat_model.md format for future analysis.

When do I need to map trust boundaries in my software architecture?

Map trust boundaries when adding features involving authentication, storage, network exposure, or third-party integrations. A structured threat model identifies these boundaries and required security guarantees before launch to prevent vulnerabilities.

Can I use threat modeling for architecture changes and new integrations?

Yes, threat modeling applies to architecture reviews, new features adding authentication or storage, and pre-deploy security assessments. It produces concise STRIDE-style coverage of assets and trust boundaries in a reusable threat_model.md summary.

What limitations exist when generating a threat_model.md for vulnerability analysis?

This threat modeling skill focuses on producing concise STRIDE-style coverage of assets and trust boundaries. It requires clear architecture context for new features or pre-deploy reviews to effectively capture reusable scan anchors and security guarantees.