security-threat-model

Generate repository-grounded threat models enumerating trust boundaries, assets, attacker capabilities, abuse paths, and mitigations.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/lev-os/lev-content --skill security-threat-model-lev-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/lev-os/lev-content/tree/main/sources/skills/security-threat-model
Command: npx skills add https://github.com/lev-os/lev-content --skill security-threat-model-lev-os

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of AppSec-grade threat models for code repositories, identifying trust boundaries, assets, attacker capabilities, abuse paths, and mitigations.

Core Features & Use Cases

  • Repository-Grounded Threat Modeling: Creates specific threat models based on codebase analysis, not generic checklists.
  • Enumerates Key Security Elements: Identifies trust boundaries, assets, attacker capabilities, abuse paths, and mitigations.
  • Use Case: When launching a new feature, use this Skill to proactively identify potential security vulnerabilities and design effective mitigations before deployment.

Quick Start

Use the security-threat-model skill to threat model the repository located at '/app/code/my-web-app'.

Frequently Asked Questions about security-threat-model

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

FAQPage Schema
How do I generate an AppSec threat model for my codebase?

To generate an AppSec threat model, point the analysis at your codebase or specific path. The tool identifies trust boundaries, assets, attacker capabilities, abuse paths, and mitigations based on repository code.

What is repository-grounded threat modeling and how does it work?

Repository-grounded threat modeling analyzes your actual codebase to identify security threats, rather than applying generic checklists. It enumerates specific trust boundaries, assets, and abuse paths found in the code.

Can I use this to identify security vulnerabilities before deploying a new feature?

Yes, you can proactively identify security vulnerabilities and design mitigations before deployment by running the threat model analysis on the specific code paths for the new feature.

Does the threat model report require any confirmation before finalizing?

Yes, the threat model report requires explicit user confirmation of assumptions and context before finalizing, ensuring the identified trust boundaries, abuse paths, and mitigations align with your environment.

What specific security elements are enumerated in the threat model?

The threat model enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations to provide a comprehensive security analysis of the targeted codebase.