security-threat-model

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

Updated May 25, 2026

Search Tags:#threat modeling #security analysis #appsec #trust boundaries #attack paths #repository review

Ready to run

npx skills add https://github.com/Yairama/mine-rs --skill security-threat-model-yairama

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/Yairama/mine-rs/tree/main/.github/skills/security-threat-model
Command: npx skills add https://github.com/Yairama/mine-rs --skill security-threat-model-yairama

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps security teams transform unfamiliar repositories into actionable threat models by identifying trust boundaries, assets, attack paths, and mitigations grounded in available code and documentation.

Core Features & Use Cases

Repository-Grounded Analysis: Builds AppSec threat models based on repository evidence instead of generic security checklists.
Threat Enumeration and Prioritization: Identifies attacker goals, abuse paths, impacted assets, likelihood, impact, and recommended mitigations.
Use Case: Analyze a software repository before a security review to produce a concise Markdown threat model covering architecture, entry points, risks, and manual review focus areas.

Quick Start

Use the security-threat-model skill to create a repository-specific threat model for the provided codebase and highlight the highest priority security risks.

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 from an existing codebase?▼

You can generate a threat model from a codebase by analyzing repository evidence to identify trust boundaries, assets, and attack paths. This approach grounds the security analysis in actual code and documentation rather than relying on generic security checklists.

What is the best way to identify attack paths and trust boundaries for application security?▼

The best way to identify attack paths and trust boundaries is through evidence-based AppSec analysis that maps attacker goals against repository assets. This process prioritizes security risks by likelihood and impact while highlighting manual review focus areas.

Can I use threat modeling for architecture assessments and abuse path analysis?▼

Yes, threat modeling applies to architecture assessments and abuse path analysis workflows. It transforms unfamiliar repositories into actionable security models by enumerating impacted assets, attacker goals, and recommended mitigations.

Does repository-grounded threat modeling produce visual system diagrams and mitigation recommendations?▼

Yes, repository-grounded threat modeling produces Mermaid system diagrams alongside concrete mitigation recommendations. It delivers a concise Markdown threat model covering architecture, entry points, and prioritized security risks for manual review.

What are the limitations of codebase threat modeling for AppSec reviews?▼

Codebase threat modeling requires explicit assumptions and available repository evidence to function accurately. It may not detect risks outside the provided codebase or fully replace manual security review without sufficient documentation and architecture context.