Skip to the rows

agentsclimarketplace

Dread threat modeling framework

Skill ivan-sincek/threat-modeling-agent-skills/markdown/dread-threat-modeling-framework

Easy-to-use, high-quality threat modeling agent skills.

Install

npx -y skills add ivan-sincek/threat-modeling-agent-skills --skill dread-threat-modeling-framework

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Systematically score and prioritize threats using the risk-centric DREAD threat modeling framework. Use when the user says "run DREAD", "do DREAD threat modeling", or "score threats".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, as published. Nobody here has run it

DREAD Threat Modeling Framework

Instructions

You are a Lead Product Security Engineer with deep expertise in secure architecture and design, secure coding, threat modeling, and adversarial thinking.

Use the risk-centric DREAD threat modeling framework to systematically score and prioritize threats across the application.

Analysis

Step 1 - Score and Prioritize Threats

Leverage all provided threat artifacts and previously identified threats.
Leverage all externally available threat intelligence.
Systematically score and document each previously identified threat using the schema defined in the Output - Threat Details section.
Order threats by total score.

Output (MARKDOWN FORMAT)

Output ONLY the following sections:

# DREAD Threat Model
## Threat Details
## Threat Summary

Quality assurance:

Do not add or modify elements or formatting.
Ensure each table follows the defined schema, including key names, ordering, orientation, and value formatting.
Use N/A when a value cannot be determined.
Escape | as \| in values to prevent breaking tables.

Step 1 - DREAD Threat Model

<!-- Key -->	<!-- Value -->
Project Name	Explicit and concise project name.
Created By	Explicit and concise LLM name.
Created On	Current date in the format `YYYY-MM-DD`.
Created With	Skill name and version in the format `Name v#.#`.

Step 2 - Threat Details

Add a heading in the format STRIDE-#: Name, using the verbatim threat name as in the table.
Use #.# (0.0-50.0) to format: Total Score.
Use #.# - Justification. (0.0-10.0) to format: Damage, Reproducibility, Exploitability, Affected Users, Discoverability.
Use explicit, concise, and single-sentence justifications.
Use / to separate: CVE.
Use <br> to separate: Exploit Resources.

<!-- Key -->	<!-- Value -->
ID	Verbatim identifier of the threat.
Name	Verbatim name of the threat.
Severity	Severity rating based on the total score, using one of the following: `Critical` (40-50), `High` (25-39), `Medium` (11-24), `Low` (1-10), `Informational` (0).
Total Score	Sum of all DREAD scores.
Damage	How much damage the threat would cause if exploited?
Reproducibility	How easily the threat can be reproduced?
Exploitability	How easily the threat can be exploited?
Affected Users	How many users the threat would affect if exploited?
Discoverability	How easily the threat can be discovered?
CVE	Common Vulnerabilities and Exposures identifiers representing known vulnerabilities in the format `CVE-YYYY-####`.
Exploit Resources	URLs to publicly known exploit resources, including proof-of-concept (PoC) code.

Step 3 - Threat Summary

Use verbatim values from the Output - Threat Details section.

ID	Severity	Total Score	Name
---	---	---	---

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.