Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Create Threat Model · tobihagemann | DecimalAI

securityby tobihagemann

Create Threat Model

tobihagemann/create-threat-model

Source tobihagemann/turbo ↗License MIT

Analyze a codebase and produce a structured threat model at .turbo/threat-model.md covering assets, trust boundaries, attack surfaces with existing mitigations, attacker stories, and calibrated severity.

NewMaintained

Automatic

Security & AppSec pack

Last verified 8/21/2026

What it changes

Passed 4 of 10 test cases with the skill, and 5 of 10 without it.

Without skill50%

With skill36%

Checks it passed that the model alone missed

Security-sensitive flows in Section 1 are listed as a bulleted list of 3 to 5 items.
System assumptions are listed within Section 2 alongside assets and trust boundaries.

2 fixed6 passed either way9 still failing5 broke

Pass-rate lift: -14 pp
Tokens: +58%
Agent turns: 0%
Response time: -20%

Model gemini-3.6-flashMeasured 8/21/2026v28 of 22 cases passed with skill · 10 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/tobihagemann-create-threat-model/SKILL.md https://app.decimal.ai/s/tobihagemann-create-threat-model/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add tobihagemann-create-threat-model, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/tobihagemann-create-threat-model/ and pins it in .decimal/skills.lock

decimalai skills add tobihagemann-create-threat-model

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/tobihagemann-create-threat-model/SKILL.md https://app.decimal.ai/s/tobihagemann-create-threat-model/SKILL.md

Raw file: /s/tobihagemann-create-threat-model/SKILL.md ↗ · machine-readable summary at /s/tobihagemann-create-threat-model.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 2

Prompt

Where should system assumptions (such as OS process isolation and entropy availability) be documented in the threat model?

What was checked, without and with the skill
Checked	Without skill	With skill
System assumptions are listed within Section 2 alongside assets and trust boundaries.	Missed	Passed

case-14 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md129 lines2 files

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.

Read the project README, AGENTS.md, and any architecture or security documentation.
Examine top-level directory structure, build files, and dependency manifests to identify modules, languages, frameworks, and deployment model.
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.
Identify security-critical dependencies (crypto libraries, auth providers, network stacks, native/FFI libraries). Note what this codebase delegates versus what it owns.
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)

For each flow found, note the relevant files and trace data from input to processing to output.

Read references/analysis-guide.md for detailed guidance by application type and platform.

Step 3: Write the Threat Model

Track record

Benchmark

4 / 10

test cases passed, vs 5 / 10 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

tobihagemann / turbo

claude/skills/create-threat-model/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v2Bundled 1 file

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Create Threat Model

Step 1: Reconnaissance

Step 2: Security-Relevant Code Discovery

Step 3: Write the Threat Model

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills