security-threat-model

Generate a repo-grounded AppSec threat model with assets, trust boundaries, and mitigations.

5.0k|454|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/tech-leads-club/agent-skills --skill security-threat-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/%28security%29/security-threat-model
Command: npx skills add https://github.com/tech-leads-club/agent-skills --skill security-threat-model

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps security engineers generate a repo-grounded threat model anchored to concrete evidence in the codebase, enabling precise risk analysis and focused reviews.

Core Features & Use Cases

  • Evidence-backed modeling: anchors architectural claims to repo paths, code, and configuration evidence.
  • Comprehensive threat coverage: enumerates assets, trust boundaries, attacker capabilities, abuse paths, mitigations, and residual risks.
  • Structured outputs: produces threat matrices, prioritized risks, and focused recommendations for manual review.
  • Targeted scopes: suitable for evaluating a repository or in-scope code paths, with explicit assumptions and open questions.

Quick Start

To begin, trigger the threat-model process for a repository or sub-path, ensuring you provide scope and any known constraints. Example: run threat-model on the root of the project to generate the initial assessment.

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 code path in my repository?

Generate a repo-grounded threat model by triggering the assessment process on a repository root or sub-path. The skill enumerates assets, trust boundaries, and abuse paths, producing a structured security report with prioritized risks.

What is repo-grounded threat modeling and how does it differ from generic AppSec reviews?

Repo-grounded threat modeling anchors architectural claims and risk assessments to concrete evidence in the codebase. Unlike generic reviews, it enforces an output contract with explicit assumptions, evidence anchors, and focused recommendations for manual review.

Can I assess AppSec risk for just a sub-path instead of the entire repository?

Yes, you can target specific code paths for evaluation. The skill accepts a scoped directory or sub-path as input, enumerates attacker capabilities and mitigations within that boundary, and highlights residual risks for manual review.

How do I document trust boundaries and attacker capabilities during a risk assessment?

Document trust boundaries and attacker capabilities by running the threat model process. It identifies assets, maps abuse paths across trust boundaries, and outputs a threat matrix with prioritized risks and mitigations anchored to repository evidence.

What assumptions and open questions are included in a generated security report?

The security report includes explicit assumptions and open questions derived from the codebase analysis. It enforces an output contract that pairs prioritized risks with evidence anchors, ensuring transparency about constraints and residual risks.

When should I not use automated threat modeling for my AppSec analysis?

Avoid automated threat modeling when the repository lacks sufficient code or configuration evidence to anchor architectural claims. The skill requires concrete repo paths to enumerate assets, trust boundaries, and mitigations accurately.