security-threat-model

Analyze codebase files to produce repository-specific threat models.

Updated May 11, 2026
One-click install
npx skills add https://github.com/guhans6/agent-workbench --skill security-threat-model-guhans6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/guhans6/agent-workbench/tree/main/shared/skills/security-threat-model
Command: npx skills add https://github.com/guhans6/agent-workbench --skill security-threat-model-guhans6

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, json, pandas, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a detailed threat model for specific repositories or codebases, helping AppSec engineers identify potential security risks and prioritize them based on impact and likelihood.

Core Features & Use Cases

  • Repository-Grounded Threat Modeling: Produces threat models that are specific to the repository or a project path, not generic checklists.
  • Evidence-Backed Findings: Every architectural claim is backed by evidence from the repository.
  • Realistic Attacker Goals: Prioritizes realistic attacker goals and concrete impacts over generic checklists.
  • Use Case: When a security engineer needs to quickly understand the security risks associated with a new repository or codebase.

Quick Start

Run the skill with the repository path and specify the branch, if necessary: security-threat-model --repo-path /path/to/repo --branch <branch-name>

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 repository-specific threat model for AppSec analysis?

To generate a repository-specific threat model for AppSec analysis, run the skill with your local repository path and specify the branch name. The tool analyzes codebase files and documentation to identify security risks.

What is repository-grounded threat modeling and how does it differ from generic checklists?

Repository-grounded threat modeling analyzes actual codebase files to produce evidence-backed findings, prioritizing realistic attacker goals over generic checklists. Every architectural claim is backed by concrete evidence from the repository.

Do I need Python and specific libraries to run security risk assessments on my codebase?

Yes, you need Python installed along with the requests, json, and pandas libraries to run these security risk assessments. These dependencies are required for the tool to parse files and structure the threat model output.

Can I use this threat modeling tool for automated AppSec workflows?

Yes, this threat modeling tool is suitable for both automated AppSec workflows and manual security reviews. It identifies trust boundaries, assets, attacker capabilities, abuse paths, and mitigations to help engineers prioritize risks.

What's the best way to analyze security risks in a new codebase?

The best way to analyze security risks in a new codebase is to use a repository-grounded tool that identifies trust boundaries and abuse paths. This provides a detailed threat model based on actual code rather than generic assumptions.

What specific security components does the threat model identify during code analysis?

During code analysis, the threat model identifies trust boundaries, assets, attacker capabilities, abuse paths, and mitigations. This helps security engineers quickly understand and prioritize potential security risks by impact and likelihood.