security-threat-model

Produces codebase-specific threat models from repository analysis.

Updated Aug 27, 2026

Search Tags:#AppSec #risk prioritization #codebase security #security threat modeling #threat enumeration

Ready to run

npx skills add https://github.com/PAISHU-AI/PAI-zong-NB --skill security-threat-model-paishu-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/PAISHU-AI/PAI-zong-NB/tree/main/skills/security-threat-model
Command: npx skills add https://github.com/PAISHU-AI/PAI-zong-NB --skill security-threat-model-paishu-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pynacl, pyjwt, aiohttp, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill produces specific and actionable threat models for given codebases, allowing developers and security engineers to identify and mitigate security risks effectively.

Core Features & Use Cases

Codebase-Specific Threat Modeling: Identifies trust boundaries, assets, attacker capabilities, abuse paths, and mitigations for a given codebase.
AppSec-Grade Output: Delivers a concise Markdown report, anchored to repository evidence and assumptions, prioritizing realistic attacker goals and impacts.
Quick Start: Use the security-threat-model Skill to generate a threat model for your codebase by providing the repository root path or subpath.

Quick Start

Generate a threat model for your repository by running security-threat-model /path/to/repo.

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 security threat model for my codebase?▼

To generate a security threat model for your codebase, you provide the repository root path or subpath. The Skill analyzes the repository content and applies predefined threat modeling logic to identify security risks.

What is threat enumeration and how does it apply to secure software architecture?▼

Threat enumeration identifies trust boundaries, assets, and attacker capabilities to build secure software architecture. It produces specific threat models that pinpoint realistic attacker goals, abuse paths, and required mitigations for a given codebase.

Can I use this threat modeling approach for risk prioritization in AppSec?▼

Yes, this approach supports AppSec risk prioritization by delivering a concise Markdown report anchored to repository evidence. It prioritizes realistic attacker goals and impacts to help developers mitigate security risks effectively.

Do I need specific dependencies like pynacl or pyjwt to perform codebase security analysis?▼

Yes, codebase security analysis requires pynacl, pyjwt, and aiohttp. These dependencies are necessary for handling secure HTTP requests and executing cryptographic tasks during the threat modeling process.

What is the best way to identify trust boundaries and abuse paths in a repository?▼

The best way to identify trust boundaries and abuse paths is by analyzing repository content against predefined threat modeling logic. This produces an actionable threat model highlighting attacker capabilities and specific security mitigations.