security-threat-model

Generate repository-specific threat models with trust boundaries and mitigations.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pingqLIN/UniText --skill security-threat-model-pingqlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/pingqLIN/UniText/tree/main/runtime/skills/security-threat-model
Command: npx skills add https://github.com/pingqLIN/UniText --skill security-threat-model-pingqlin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

Core Features & Use Cases

  • Anchor architectural claims to evidence in the repository (paths, files, and config snippets).
  • Enumerate trust boundaries, assets, attacker capabilities, and abuse paths with evidence-backed claims.
  • Produce a prioritized threat model with likelihood/impact reasoning and concrete mitigations.
  • Generate a compact Mermaid diagram illustrating components and trust boundaries.
  • Provide a structured output suitable for review and follow-up actions.

Quick Start

Prompt the user to request a threat model for a given repo path, then execute the workflow to produce a repository-focused threat model grounded in repo evidence.

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 for a specific codebase?

To generate a repository-specific threat model, you prompt the tool with a target codebase path. It analyzes the codebase artifacts to enumerate trust boundaries, assets, attacker capabilities, and abuse paths, outputting a concise Markdown threat model with evidence anchors.

What is repository-grounded threat modeling in AppSec?

Repository-grounded threat modeling in AppSec is the process of anchoring architectural claims and threat enumerations to actual evidence within the codebase. It identifies trust boundaries and abuse paths using repository files, paths, and config snippets rather than relying solely on abstract design diagrams.

How do I identify trust boundaries and attack surfaces in my application?

You identify trust boundaries and attack surfaces by analyzing data flows and architectural components within your repository context. The tool automatically extracts evidence from paths and config snippets to map where trust levels change and where attackers might interact with the system.

Does this threat modeling approach work for general code review and architecture summaries?

No, this approach does not work for general code review or architecture summaries. It is explicitly designed to trigger only when you need to perform AppSec threat modeling, enumerate threats, or map abuse paths within a specific repository context.

What outputs and formats are generated during the threat modeling process?

The threat modeling process generates a structured Markdown document containing a prioritized threat model with likelihood and impact reasoning. It also includes a compact Mermaid diagram illustrating components and trust boundaries, along with concrete mitigations and evidence anchors.