security-threat-model

Generate repository-grounded threat models with components, trust boundaries, and risk rankings.

Updated Nov 29, 2025
One-click install
npx skills add https://github.com/thimslugga/agent-skills --skill security-threat-model-thimslugga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/development/security-threat-model
Command: npx skills add https://github.com/thimslugga/agent-skills --skill security-threat-model-thimslugga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling for codebases that anchors architectural claims to repository evidence, enabling precise, repository-grounded security analyses and repeatable threat models.

Core Features & Use Cases

  • Evidence-grounded system model: derives components, data flows, and trust boundaries directly from the repository.
  • Threat enumeration and risk ranking: identifies abuse paths and prioritizes threats with justification.
  • Structured output: produces a repo-specific threat model with entry points, mitigations, and monitoring guidance.
  • Template-aligned prompts: ensures compatibility with standard threat-model prompts and templates.

Quick Start

Provide the repository path or scope and trigger the threat-model workflow to generate a repo-specific threat model for review.

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 my codebase?

To generate a threat model for your codebase, provide the repository path to trigger a workflow that derives system components, data flows, trust boundaries, and abuse paths directly from the repository evidence.

What is repository-grounded threat modeling?

Repository-grounded threat modeling anchors architectural claims to actual codebase evidence, enabling precise security analyses that identify attacker capabilities, assets, and risk rankings with explicit assumptions.

How do I identify trust boundaries and entry points for AppSec risk analysis?

Identify trust boundaries and entry points for AppSec risk analysis by analyzing repository structure to derive evidence-grounded system models, enumerating abuse paths, and prioritizing threats with justifications.

Can I use standard threat model templates with repository-derived security assessments?

Yes, you can use standard threat model templates because the workflow produces template-aligned prompts and structured outputs compatible with standard threat-model formats for review.

Does threat modeling work without external dependencies for security assessments?

Threat modeling works without external dependencies for security assessments, requiring only a repository path or scope to generate a structured model with mitigations and monitoring guidance.

What is included in a repo-specific threat model output?

A repo-specific threat model output includes identified system components, trust boundaries, assets, attacker capabilities, abuse paths, risk ranking, mitigations, explicit assumptions, and open questions.