skills.rest
lidge-jun
lidge-junCOMMUNITY
Explore all skills by this author →
𝕏@claudeebumGitHub

security-threat-model

Generate repository-grounded threat models with trust boundaries, assets, and abuse paths.

5|Updated Feb 26, 2026
Search Tags:#code analysis#security#risk assessment#appsec#threat model#abuse path
One-click install
npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill security-threat-model-lidge-jun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/security-threat-model
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill security-threat-model-lidge-jun

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of repository-grounded threat models, identifying trust boundaries, assets, attacker capabilities, abuse paths, and mitigations to proactively secure your codebase.

Core Features & Use Cases

  • Automated Threat Modeling: Generates detailed threat models based on repository code and architecture.
  • Abuse Path Enumeration: Identifies concrete attack sequences and their potential impact.
  • Use Case: When developing a new microservice, use this Skill to generate a threat model that outlines potential vulnerabilities and necessary security controls before deployment.

Quick Start

Use the security-threat-model skill to generate a threat model for the current repository.

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 a threat model directly from my repository code?▼

To generate a repository-grounded threat model, trigger the threat modeling task to analyze code structure, identify trust boundaries, enumerate assets, and detail abuse paths with recommended mitigations.

What is an abuse path in application security threat modeling?▼

An abuse path is a concrete attack sequence identified during threat modeling that maps out an attacker's capabilities and potential impact against enumerated assets across trust boundaries in your codebase.

How do I conduct a proactive risk assessment before deploying a new microservice?▼

You can conduct a proactive risk assessment by running an automated threat modeling task against the microservice repository to identify vulnerabilities and define necessary security controls prior to deployment.

Can I use this threat modeling approach without setting up external dependencies?▼

Yes, this threat modeling approach requires no external dependencies and operates directly on your repository structure to identify assets, trust boundaries, and mitigations.

Does automated threat modeling replace manual code analysis for finding vulnerabilities?▼

Automated threat modeling complements manual code analysis by systematically enumerating assets, attacker capabilities, and abuse paths, providing a structured output contract to guide deeper manual security reviews.

Related Skills

Explore More Software Engineering Skills→
vKenjovKenjo

security-threat-model

Enumerate trust boundaries, assets, and attack paths in a codebase.

Community
Advanced
jeffpeckyjeffpecky

security-threat-model

Generate a Markdown threat model from a codebase or project path.

Community
Advanced
heyzudeheyzude
4

security-threat-model

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

Community
Advanced
3commas-io3commas-io
4

stride-analysis-patterns

Apply STRIDE methodology to identify security threats in system designs.

Official
Advanced