security-threat-model

Enumerate trust boundaries, assets, attacker capabilities, abuse paths, and mitigations into a Markdown report.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/coff33ninja/ai-skills-mcp --skill security-threat-model-coff33ninja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/coff33ninja/ai-skills-mcp/tree/main/skills/security-threat-model
Command: npx skills add https://github.com/coff33ninja/ai-skills-mcp --skill security-threat-model-coff33ninja

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured approach to threat modeling, helping you identify potential security risks in a codebase or project path.

Core Features & Use Cases

  • Repository-Grounded Threat Modeling: Enumerate trust boundaries, assets, attacker capabilities, abuse paths, and mitigations.
  • Markdown Report: Outputs a concise Markdown threat model that is easy to review and understand.
  • Use Case: Use this Skill to create a threat model for a specific repository or project path, and get a prioritized list of threats and recommended mitigations.

Quick Start

Use the security-threat-model skill to create a threat model for the 'my-project' 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 create a threat model for a specific code repository?

A repository-grounded threat model requires evidence from your codebase to enumerate trust boundaries, assets, and abuse paths. This Skill generates a Markdown report detailing prioritized threats and recommended mitigations based on repository evidence.

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

Repository-grounded threat modeling identifies security risks by enumerating trust boundaries, assets, and attacker capabilities directly from a codebase. It outputs a concise Markdown report requiring user validation of assumptions and evidence from the repository.

Can I use this threat modeling approach for AppSec analysis on any project path?

This threat modeling approach is suitable for AppSec engineers and security analysts analyzing any repository or project path. It produces a concise Markdown report containing prioritized abuse paths and mitigations tailored to the specific codebase.

What is the best way to document security threats and mitigations for a codebase?

Documenting security threats is best achieved by generating a concise Markdown report that details trust boundaries, assets, and prioritized abuse paths. This format ensures the threat model is easy to review, understand, and share with security stakeholders.

Do I need to validate assumptions when generating a threat model report?

Validating assumptions is required when generating a threat model report because the analysis relies on evidence from the repository. User validation ensures the enumerated abuse paths and mitigations accurately reflect the project's security posture.