security-threat-model

Generates repository-grounded threat models with trust boundaries, abuse paths, and prioritized mitigations.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/IagoPrandi/zeroclaw-plugin --skill security-threat-model-iagoprandi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/IagoPrandi/zeroclaw-plugin/tree/main/.claude/skills/security-threat-model
Command: npx skills add https://github.com/IagoPrandi/zeroclaw-plugin --skill security-threat-model-iagoprandi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security teams need threat models that reflect the actual codebase rather than generic checklists, but manually mapping trust boundaries, assets, and abuse paths across a repository is slow and error-prone. ## Core Features & Use Cases - Evidence-Anchored Analysis: Enumerates components, trust boundaries, entry points, and assets with every claim tied to a repo path or symbol. - Prioritized Threat Enumeration: Produces concrete multi-step abuse paths with qualitative likelihood, impact, and critical/high/medium/low priority ratings. - Structured Output Contract: Writes a concise Markdown threat model with a Mermaid diagram, threat table, and focus paths for manual security review. - Use Case: Point the Skill at a service repository before a launch review to get an AppSec-grade threat model listing the top abuse paths, existing controls with evidence, and the files that merit deeper manual audit. ## Quick Start Ask the assistant to threat model this repository and produce a prioritized Markdown report of 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 create a threat model for a codebase?▼

Provide the repository root path and any in-scope directories, then ask for a threat model. The Skill maps components, trust boundaries, and entry points from repo evidence, asks clarifying questions about deployment and exposure, then writes a prioritized Markdown report.

What does a repo-grounded threat model include?▼

The output includes an executive summary, system model with a Mermaid diagram, asset and attacker models, entry point tables, 5-10 abuse paths, a threat table with stable TM-001 style IDs, criticality calibration, and focus paths for manual security review.

When should I trigger threat modeling versus a code review?▼

Trigger it only when you explicitly want threats, abuse paths, or AppSec threat modeling for a codebase or path. It is not intended for general architecture summaries, routine code review, or non-security design work.

Does the threat model rely on assumptions about my deployment?▼

Yes, and it handles them explicitly. Before the final report it lists key assumptions and asks 1-3 targeted questions about deployment model, internet exposure, authn/authz, and data sensitivity, then waits for your answers.

What are the limitations of automated threat modeling?▼

The analysis is only as grounded as the repository evidence and context provided; missing deployment details become explicit assumptions that can shift risk rankings. It prioritizes realistic attacker goals but does not replace deep manual review of the focus paths it identifies.