skills.rest
dougdliu
dougdliuCOMMUNITY
Explore all skills by this author →
GitHub

security-threat-model

Identify components, data stores, and trust boundaries to generate a Markdown threat model.

Updated May 8, 2026
Search Tags:#risk-assessment#threat-modeling#appsec#repository-analysis#threat-model#security-review#mitigations
One-click install
npx skills add https://github.com/dougdliu/FRC_AI_Mega_Project --skill security-threat-model-dougdliu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/dougdliu/FRC_AI_Mega_Project/tree/main/skills/codex/security-threat-model
Command: npx skills add https://github.com/dougdliu/FRC_AI_Mega_Project --skill security-threat-model-dougdliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repository-grounded threat modeling unifies evidence-based risk assessment for codebases and paths, ensuring security concerns are identified early and actionable.

Core Features & Use Cases

  • Anchor threats to assets, trust boundaries, and entry points within the repository.
  • Produce an actionable threat model with evidence references and prioritized mitigations.
  • Use cases include threat modeling a codebase before release, or auditing a module or path for AppSec vulnerabilities.

Quick Start

Provide the repository root path and in-scope paths, then request a repository-grounded threat model for the specified code path.

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 directly from my repository code?▼

To create a repository-grounded threat model, provide the repository root path and in-scope code paths. The analysis identifies primary components, data stores, and trust boundaries to anchor an evidence-backed security review.

What is evidence-based threat modeling for application security?▼

Evidence-based threat modeling unifies risk assessment by anchoring identified threats to concrete assets, entry points, and code paths within the repository. This ensures security concerns are identified early and mapped to actionable, prioritized mitigations.

How do I identify trust boundaries and entry points for an AppSec review?▼

Identifying trust boundaries and entry points involves analyzing in-scope code paths to enumerate assets and attacker capabilities. The process maps these elements to concrete risks and abuse paths within the repository.

Can I audit a specific module for security vulnerabilities before release?▼

Yes, you can audit a specific module before release by specifying the in-scope code paths. The threat model focuses on the targeted module to produce a concise Markdown output with prioritized risks and mitigations.

Does repository-grounded threat modeling work without external dependencies?▼

Yes, repository-grounded threat modeling works without external dependencies. It analyzes the provided repository paths directly to extract components, data stores, and trust boundaries for the security assessment.

Related Skills

Explore More Software Engineering Skills→
ollieb89ollieb89

security-threat-model

Identify assets, trust boundaries, entry points, and data flows in a repository.

Community
Advanced
koki3141koki3141
2

security-threat-model

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

Community
Advanced
northseadlnorthseadl

security-threat-model

Generate repository-grounded threat models identifying trust boundaries, assets, and abuse paths.

Community
Advanced
alanharrryy-wqalanharrryy-wq
2

security-threat-model

Generate repository-grounded AppSec threat models with prioritized threats and Mermaid diagrams.

Community
Advanced