threat-modeling

threat-modeling is a skill for Claude Code, Codex from Security-Phoenix-demo/security-skills-claude-code. It costs 0 tokens per session (4,057 once invoked), scanned A, original, MIT.

A threat-modeling skill analyzes code and system architecture to identify security threats using STRIDE and DREAD, two structured security-assessment methods.

In plain words
What is it for?
Use it to assess a whole repository, a feature, a component, or an architecture diagram, including threats involving identity, data integrity, and system boundaries.
Why use it?
It helps reveal possible attacks and weaknesses during security reviews, architecture planning, or compliance work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to assess a whole repository, a feature, a component, or an architecture diagram, including threats involving identity, data integrity, and system boundaries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/security-phoenix-demo/security-skills-claude-code/threat-modeling
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Security-Phoenix-demo/security-skills-claude-code --skill threat-modeling
Clone the repo
git clone --depth 1 https://github.com/Security-Phoenix-demo/security-skills-claude-code

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for threat-modeling

README.md
[![agentmods](https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/threat-modeling/github.svg)](https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/threat-modeling)
Your own site
<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/threat-modeling"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/threat-modeling/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for threat-modeling

Your own site · 80×15
<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/threat-modeling"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/threat-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,057 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.04057
Opus 5 $0.00000 $0.02028
Sonnet 5 $0.00000 $0.00811
Haiku 4.5 $0.00000 $0.00406

Measured 10d ago against content hash 24b67a49de99, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

threat-modeling scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST http://localhost:8090/api/v1/threat-model/assessments \
skills/Security Assessment/threat-modeling/SKILL.md · 573 lines

How it starts

The opening of the file, as written. The whole thing — 573 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Threat Modeling Agent Skill

Purpose: Automated threat modeling from code analysis using STRIDE/DREAD methodologies

When to use: Security assessment, architecture review, compliance documentation, attack scenario planning


Workflow

1. Scope Determination

Determine analysis scope:

  • Full repository threat model
  • Feature-specific threat model
  • Component-level threat model
  • Architecture diagram analysis

Check prerequisites:

  • Repository is indexed in knowledge graph
  • Business context available (optional)
  • Architecture diagrams uploaded (optional)
  • CVE intelligence data available (optional)

2. Architecture Extraction

Extract system architecture from:

  • Knowledge graph clusters (components)
  • Call chains (data flows)
  • Entry points (public APIs)
  • Trust boundaries (zone crossings)
  • Technology stack
  • External dependencies

Enrich with:

  • Architecture diagram analysis (AI vision)
  • Business context (industry, compliance)
  • Deployment context (cloud infrastructure)

3. STRIDE Threat Analysis

Generate threats for each category:

  • Spoofing: Identity and authentication threats
  • Tampering: Data and code integrity threats
  • Repudiation: Audit and accountability threats
  • Information Disclosure: Data leakage threats
  • Denial of Service: Availability threats
  • Elevation of Privilege: Access control threats

For each threat, identify:

  • Affected components
  • Affected data flows
  • Trust boundary crossings
  • Attack vectors
  • Prerequisites
  • Detection methods

4. DREAD Risk Assessment

Score each threat (1-10):

  • Damage Potential
  • Reproducibility
  • Exploitability
  • Affected Users
  • Discoverability

Calculate:

  • Risk Score = Average of 5 dimensions
  • Risk Level = Critical/High/Medium/Low

5. Phoenix Intelligence Enrichment

Enrich with Phoenix data (IP-protected):

  • Related CVEs
  • Phoenix proprietary scores (high-level only)
  • Threat actor data
  • MITRE ATT&CK techniques
  • CAPEC attack patterns

Read the full file on GitHub · 573 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 573 lines · 0 tokens per session scan A 24b67a49de99

Subscribe to this mod's changes

threat-modeling is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,057 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens