Threat Library

Build and maintain a reusable threat library tailored to your organization, platform, and threat landscape. Use when cataloging threats for future analyses, threat modeling sessions, and architecture reviews.

48 stars 10 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill threat-library
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/threat-modeling/skills/threat-library ~/.claude/skills/threat-library

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Threat Library

Create a curated, reusable library of threats relevant to your organization and technology stack.

## Context

You are a senior security architect building a threat library for $ARGUMENTS. A well-maintained threat library accelerates future threat modeling and ensures consistency.

## Domain Context

- **Library Organization**: By STRIDE category, by platform/technology (web app, cloud, mobile), by attack vector (network, social engineering, supply chain), or by attack technique (MITRE ATT&CK)
- **Threat Maturity**: Distinguish between theoretical threats (possible but never observed) and mature threats (known attack patterns, CVEs, public exploits)
- **Customization**: Generic threat libraries exist (OWASP Top 10, MITRE ATT&CK), but organization-specific threats (e.g., "privilege escalation via legacy auth system") are more valuable
- **Versioning & Review**: Threat libraries should be reviewed annually; add new threats as vulnerabilities emerge, remove obsolete threats as mitigations deploy

## Instructions

1. **Define Threat Taxonomy**: Decide how to organize threats:
   - **Option A (STRIDE)**: Organize by threat category; most useful for STRIDE threat modeling
   - **Option B (MITRE ATT&CK)**: Organize by adversary tactic/technique; most useful for defender detection and response
   - **Option C (Technology)**: Organize by platform (web, cloud, mobile, IoT); useful for architecture reviews
Read the full skill on GitHub

Details

Skill name
threat-library
Path
security/threat-modeling/skills/threat-library/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Threat Library skill do?

Build and maintain a reusable threat library tailored to your organization, platform, and threat landscape. Use when cataloging threats for future analyses, threat modeling sessions, and architecture reviews.

How do I install the Threat Library skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Threat Library popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.