security-threat-model

Identify components, data stores, entry points, and trust boundaries from repository evidence.

Updated Mar 17, 2026

Search Tags:#security #threat-modeling #appsec #risk-analysis #trust-boundaries #abuse-paths #evidence-anchor

Ready to run

npx skills add https://github.com/jaypatrick/skills --skill security-threat-model-jaypatrick

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/jaypatrick/skills/tree/main/security-threat-model
Command: npx skills add https://github.com/jaypatrick/skills --skill security-threat-model-jaypatrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling is often ad-hoc and disconnected from the actual codebase. This Skill provides a repository-backed approach that anchors threats, assets, and trust boundaries to concrete repo evidence to guide AppSec work.

Core Features & Use Cases

Repository-grounded threat modeling with explicit evidence anchors
Systematic enumeration of assets, boundaries, and abuse paths
Actionable mitigations mapped to concrete repo locations and controls

Quick Start

Generate a repository-grounded threat model for the codebase using the provided evidence anchors.

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 grounded in my codebase?▼

Repository-grounded threat modeling anchors threats, assets, and trust boundaries to concrete code evidence, avoiding ad-hoc analysis. It systematically enumerates assets, entry points, attacker capabilities, and abuse paths to guide AppSec work with actionable mitigations.

How do I identify trust boundaries and abuse paths in my application?▼

You can anchor architectural claims and identified threats to specific repository files and paths. This provides concrete mitigations mapped to exact repo locations and controls, along with validation steps and a focus path for manual review.

Can I use repository evidence to prioritize AppSec risks?▼

Repository-grounded threat modeling systematically enumerates assets, trust boundaries, attacker capabilities, and abuse paths. It anchors every architectural claim to codebase evidence, ensuring risks are analyzed with explicit likelihood and impact reasoning.

What is the best way to anchor threat modeling to actual code?▼

The modeling process provides concrete mitigations mapped to specific repo locations and controls, along with validation steps. It also delivers a focus path for manual review, ensuring all identified threats are actionable within the codebase.