threat-modeling

threat-modeling is a skill for Claude Code, Codex from Omar-Obando/qwen-orchestrator. It costs 59 tokens per session (2,589 once invoked), scanned A, original, MIT.

A guide to finding and assessing security threats in an application or system. It covers attack paths and structured methods such as STRIDE, DREAD, and attack trees.

In plain words
What is it for?
Use it to model threats for web apps, APIs, cloud systems, mobile apps, microservices, and IoT systems.
Why use it?
It helps identify how a system could be attacked and turn those risks into security requirements and mitigation plans before problems reach production.

Skill for Claude CodeCodex

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

Good fit Use it to model threats for web apps, APIs, cloud systems, mobile apps, microservices, and IoT systems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/omar-obando/qwen-orchestrator/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 Omar-Obando/qwen-orchestrator --skill threat-modeling
Clone the repo
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestrator

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/omar-obando/qwen-orchestrator/threat-modeling/github.svg)](https://agentmods.dev/skills/omar-obando/qwen-orchestrator/threat-modeling)
Your own site
<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/threat-modeling"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/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/omar-obando/qwen-orchestrator/threat-modeling"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/threat-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,589 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00059 $0.02589
Opus 5 $0.00030 $0.01295
Sonnet 5 $0.00012 $0.00518
Haiku 4.5 $0.00006 $0.00259

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

Security

Grade A, and why

threat-modeling scanned grade A with 0 findings 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 9d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/threat-modeling/SKILL.md · 291 lines

How it starts

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

Threat Modeling Skill — Cybersecurity Engineer

Overview

This skill provides comprehensive guidance for threat modeling and security analysis. It covers threat identification, attack vector analysis, threat model creation, and threat mitigation following CISSP and CSSLP certifications and OWASP threat modeling standards.

When to Use

Use this skill when:

  • Performing threat modeling for systems
  • Identifying security threats and vulnerabilities
  • Analyzing attack vectors and attack paths
  • Creating threat models for applications
  • Implementing STRIDE threat modeling
  • Using DREAD risk assessment
  • Creating attack trees
  • Performing threat modeling workshops
  • Identifying security requirements
  • Creating threat mitigation strategies
  • Documenting threat models
  • Performing threat modeling for APIs
  • Creating threat models for microservices
  • Performing threat modeling for cloud systems
  • Identifying insider threats
  • Analyzing supply chain threats
  • Creating security requirements
  • Performing threat modeling for mobile apps
  • Identifying data flow threats
  • Creating threat models for IoT systems
  • Performing threat modeling for web applications
  • Identifying authentication threats
  • Analyzing authorization threats
  • Creating threat models for databases

Do NOT use this skill when:

  • Writing application business logic (use domain-driven skill)
  • Designing database schemas (use database-design skill)
  • Writing API endpoint specifications (use api-design skill)
  • Performing general code review (use code-review skill)
  • Writing SQL queries (use sql-best-practices skill)
  • Designing multi-page website layouts (use design-system skill)
  • Analyzing deployment configurations (use deployment skill)
  • Writing documentation (use documentation-best-practices skill)

Threat Modeling Frameworks

STRIDE Model

┌─────────────────────────────────────────────────────────────┐
│              STRIDE Threat Modeling                         │
├─────────────────────────────────────────────────────────────┤
│  S - Spoofing Identity:                                     │
│  - Impersonating users or systems                           │
│  - Attack examples: Credential theft, token theft           │
│  - Mitigations: Authentication, MFA, certificates           │
│                                                              │
│  T - Tampering with Data:                                   │
│  - Modifying data in transit or at rest                     │
│  - Attack examples: Data manipulation, code injection       │
│  - Mitigations: Integrity checks, digital signatures        │
│                                                              │
│  R - Repudiation:                                           │
│  - Actions cannot be traced to actor                        │
│  - Attack examples: Denying actions, log tampering          │
│  - Mitigations: Audit logging, non-repudiation              │
│                                                              │
│  I - Information Disclosure:                                │
│  - Unauthorized access to information                       │
│  - Attack examples: Data breaches, eavesdropping            │
│  - Mitigations: Encryption, access controls                 │
│                                                              │
│  D - Denial of Service:                                     │
│  - Service unavailable to legitimate users                  │
│  - Attack examples: DDoS, resource exhaustion               │
│  - Mitigations: Rate limiting, redundancy                   │
│                                                              │
│  E - Elevation of Privilege:                                │
│  - Gaining higher privileges than intended                  │
│  - Attack examples: Privilege escalation, code execution    │
│  - Mitigations: Least privilege, access controls            │
└─────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 291 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 291 lines · 59 tokens per session scan A eff09074fde9

Subscribe to this mod's changes

threat-modeling is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 2,589 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.