agentmods.dev

create-threat-model

create-threat-model is a skill for Claude Code from tobihagemann/turbo. It costs 48 tokens per session (2,083 once invoked), scanned A, original, MIT.

A workflow for describing a codebase's security risks in a threat model, a document covering valuable assets, trust boundaries, attack paths, defenses, and severity.

In plain words
What is it for?
Use it to analyze an application or selected modules and produce a threat-model document that records what needs protection, where attackers may enter, and what defenses already exist.
Why use it?
It gives you a structured picture of how the current system could be attacked without mixing the description with proposed fixes.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

Part of the turbo plugin — 71 skills shipped together

not rated 420repo +1 changed 3d ago A scan SkillSpector: pass 48 tokens original MIT

Good fit Use it to analyze an application or selected modules and produce a threat-model document that records what needs protection, where attackers may enter, and what defenses already exist.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tobihagemann/turbo/create-threat-model
View source ↗ tobihagemann/turbo
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 tobihagemann/turbo --skill create-threat-model
Clone the repo
git clone --depth 1 https://github.com/tobihagemann/turbo

Made for: Claude Code.

Or install turbo, the plugin that ships this one along with the rest of its 71 skills.

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 create-threat-model

README.md
[![agentmods](https://agentmods.dev/badge/skills/tobihagemann/turbo/create-threat-model/github.svg)](https://agentmods.dev/skills/tobihagemann/turbo/create-threat-model)
Your own site
<a href="https://agentmods.dev/skills/tobihagemann/turbo/create-threat-model"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/create-threat-model/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 create-threat-model

Your own site · 80×15
<a href="https://agentmods.dev/skills/tobihagemann/turbo/create-threat-model"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/create-threat-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,083 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00048 $0.02083
Opus 5.5 $0.00019 $0.00833
Sonnet 5.5 $0.00010 $0.00417
Haiku 4.5 $0.00005 $0.00208

Measured 3d ago against content hash 898fb6d93b9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-threat-model 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 3d 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.

claude/skills/create-threat-model/SKILL.md · 135 lines

How it starts

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

Create Threat Model

Analyze the current codebase and produce a structured threat model at .turbo/threat-model.md.

The threat model describes the current state of the codebase: what it protects, where trust boundaries are, how it can be attacked, what defenses exist, and how severe each risk is. It is descriptive, not prescriptive. Do not include remediation recommendations.

Optional: $ARGUMENTS may specify scope (directories, modules, or focus areas). When scope is provided, limit reconnaissance and code discovery to the specified directories or modules. Still produce all four sections, but title the overview to reflect the narrowed scope and note what is excluded.

Step 1: Reconnaissance

Build a mental model of the system before analyzing threats.

  1. Read the project README, CLAUDE.md, and any architecture or security documentation.
  2. Examine top-level directory structure, build files, and dependency manifests to identify modules, languages, frameworks, and deployment model.
  3. Classify the application type: library, CLI tool, web service, desktop app, mobile app, or hybrid. This determines which threat categories and trust boundary patterns apply.
  4. Identify security-critical dependencies (crypto libraries, auth providers, network stacks, native/FFI libraries). Note what this codebase delegates versus what it owns.
  5. Read any existing security documentation: SECURITY.md, audit reports, threat models, or changelog entries mentioning CVEs.

Step 2: Security-Relevant Code Discovery

Search the codebase for code that handles security-sensitive operations. Do not read every file. Use targeted searches.

Categories to search for:

  • Authentication and authorization (login, OAuth, tokens, sessions, RBAC, API keys)
  • Cryptographic operations (encryption, signing, hashing, key generation, key derivation)
  • Secret and credential storage (keychains, vaults, env vars, config files with secrets)
  • Network communication (HTTP clients, TLS configuration, certificate handling, WebSocket, gRPC)
  • Untrusted input processing (file parsing, deserialization, XML/JSON/YAML from external sources)
  • IPC and process boundaries (sockets, pipes, CLI subprocesses, shared memory)
  • Plugin and extension loading (dynamic imports, ServiceLoader, plugin directories)
  • Update and distribution mechanisms (auto-update, download verification, signature checking)
  • Implicit network behavior (link previews, auto-fetches, thumbnail generation triggered by remote data)
  • Native code / FFI boundaries (C interop, JNI, ctypes, unsafe blocks, bridging headers)

Read the full file on GitHub · 135 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. 3d ago Changed · -42 tokens per session 898fb6d93b9a
  2. 2mo ago First seen · 135 lines · 90 tokens per session scan A 776796c41aad

Subscribe to this mod's changes

create-threat-model is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,083 once invoked, about $0.0002 per session on Opus 5.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-08-30.

Claude CodeSecurityagent-skillsclaude-skillscodexdeveloper-toolsskills
Related

create-threat-model compared with skills from other repositories

create-threat-model next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-threat-modeltobihagemann/turboSkill420todayMITA48Claude Code
offensive-c2-frameworksSnailSploit/Claude-RedSkill11kyesterdayMITA250Claude Code, Codex
offensive-crypto-attacksSnailSploit/Claude-RedSkill11kyesterdayMITA261Claude Code, Codex
offensive-parameter-pollutionSnailSploit/Claude-RedSkill11kyesterdayMITA0Claude Code, Codex
offensive-z-waveSnailSploit/Claude-RedSkill11kyesterdayMITA113Claude Code, Codex
fiscalisteromainsimon/paperasseSkill2.6ktodayMITA306Claude Code
comptableromainsimon/paperasseSkill2.6ktodayMITA248Claude Code