security-threat-model

Name: security-threat-model
Availability: InStock
Author: pawan0631

Generate repository-specific threat models with evidence anchors and prioritized mitigations.

Updated May 25, 2026

Search Tags:#security #evidence #risk-assessment #threat-modeling #appsec #trust-boundaries #repo-security

Ready to run

npx skills add https://github.com/pawan0631/AI_OpenAISkill --skill security-threat-model-pawan0631

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/pawan0631/AI_OpenAISkill/tree/main/skills/.curated/security-threat-model
Command: npx skills add https://github.com/pawan0631/AI_OpenAISkill --skill security-threat-model-pawan0631

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repository-grounded threat modeling that anchors architectural claims to evidence in the repo, producing actionable AppSec-grade threat models tailored to the codebase.

Core Features & Use Cases

Identify primary components, data stores, and external integrations.
Enumerate trust boundaries, assets, and entry points.
List attacker capabilities, abuse paths, and calibrate risk with explicit likelihood and impact.
Produce prioritized threats, mitigations, and repo-relative focus paths for manual review.
Ground every claim with repository evidence and explicit assumptions, using the provided prompt template and evidence anchors.

Quick Start

Provide repo inputs and trigger the threat modeling workflow to generate an evidence-backed threat model with prioritized abuse paths and mitigations.

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 grounded in my repository codebase?▼

Repository-grounded threat modeling anchors every architectural claim to evidence in your codebase, producing an AppSec-grade threat model that identifies components, trust boundaries, assets, and prioritized mitigations tailored to your repository.

What is repository-grounded threat modeling for AppSec?▼

How do I identify trust boundaries and attacker capabilities during risk assessment?▼

Run the threat modeling workflow to enumerate trust boundaries, assets, and entry points, which then maps attacker capabilities and abuse paths to calibrate explicit risk likelihood and impact for your application security review.

Does this threat modeling approach require external dependencies or components?▼

No, this threat modeling approach requires no external dependencies or components. You provide the code repository inputs, and the workflow generates the threat model using its internal prompt template and evidence anchors.

Can I use this for manual AppSec review focus paths in my code?▼

Yes, the output includes repo-relative focus paths and actionable mitigations, directing your manual AppSec review toward the most prioritized threats identified during the codebase analysis.

What is the best way to document assumptions when threat modeling a code repository?▼

Use a threat modeling approach that enforces explicit assumptions alongside evidence anchors, ensuring every architectural claim and risk ranking is grounded in verifiable codebase artifacts for your security analysis.