security-threat-model

Identify runtime components, data flows, trust boundaries, and entry points for AppSec threat modeling.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill security-threat-model-yu-iskw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/yu-iskw/dbt-artifacts-parser-ts/tree/main/.codex/skills/security-threat-model
Command: npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill security-threat-model-yu-iskw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Repository-grounded threat modeling that anchors architectural claims to evidence in the codebase and related artifacts, enabling focused AppSec analysis and risk prioritization.

Core Features & Use Cases

  • Repo-grounded modeling workflow that maps components, data flows, trust boundaries, assets, and attacker goals to concrete evidence in the repository.
  • Generates prioritized threats and actionable mitigations tailored to the repository's structure and usage scenarios.
  • Produces a structured threat model report suitable for security reviews and compliance engagement, with explicit assumptions and open questions.

Quick Start

Invoke the threat-model workflow against the target repository to produce a detailed AppSec threat model anchored to repository 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 create a threat model from an existing repository?

AppSec threat modeling for a repository involves identifying runtime components, data flows, and trust boundaries, then anchoring those architectural claims to concrete code evidence. It produces a structured report with prioritized risks, mitigations, and actionable review paths.

How do I identify trust boundaries and data flows for application security review?

Identifying trust boundaries and data flows for an application security review requires mapping the repository's runtime components and entry points. This Skill surfaces evidence anchors tied to repo paths and configs to ground the AppSec analysis in actual codebase artifacts.

Can I generate a structured threat model report for compliance engagement?

Yes, you can generate a structured threat model report suitable for compliance engagement and security reviews. The report includes prioritized threats, actionable mitigations, explicit assumptions, and open questions tailored to the repository's structure and usage scenarios.

What is the best way to anchor threat modeling risks to actual codebase evidence?

The best way to anchor threat modeling risks to codebase evidence is to map architectural claims directly to repository paths, configs, and code references. This approach enables focused AppSec analysis and risk prioritization while surfacing explicit assumptions.

Does this threat modeling approach require external dependencies or specific platforms?

No, this threat modeling approach requires no external dependencies. It operates directly against the target repository to model components and data flows, producing a detailed AppSec threat model anchored to the repository's own evidence and artifacts.