Design & media

security-threat-model

Try it

Produces a repository-specific AppSec threat model as a Markdown file, with every claim tied to code evidence.

What it does

Walks a repo or a chosen subpath and builds a system model from its components, data stores, entry points, and external integrations, separating runtime behavior from CI and test tooling. It then derives trust boundaries, assets, and attacker capabilities, enumerates threats as abuse paths, and ranks them by qualitative likelihood and impact. Before writing the report it pauses to confirm assumptions with you, then outputs a concise Markdown file named after the repo root or in-scope directory, following the output contract in references/prompt-template.md.

When to use it

  • Threat modeling a service before a security review or launch
  • Enumerating abuse paths for a specific upload, parser, or admin surface
  • Documenting trust boundaries and existing controls for an inherited codebase
  • Turning an architecture summary into a prioritized list of mitigations tied to code locations

The skill document

Threat Model Source Code Repo

Deliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.

Quick start

  1. Collect (or infer) inputs:
  • Repo root path and any in-scope paths.
  • Intended usage, deployment model, internet exposure, and auth expectations (if known).
  • Any existing repository summary or architecture spec.
  • Use prompts in references/prompt-template.md to generate a repository summary.
  • Follow the required output contract in references/prompt-template.md. Use it verbatim when possible.

Workflow

1) Scope and extract the system model

  • Identify primary components, data stores, and external integrations from the repo summary.
  • Identify how the system runs (server, CLI, library, worker) and its entrypoints.
  • Separate runtime behavior from CI/build/dev tooling and from tests/examples.
  • Map the in-scope locations to those components and exclude out-of-scope items explicitly.
  • Do not claim components, flows, or controls without evidence.

2) Derive boundaries, assets, and entry points

  • Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.
  • List assets that drive risk (data, credentials, models, config, compute resources, audit logs).
  • Identify entry points (endpoints, upload surfaces, parsers/decoders, job triggers, admin tooling, logging/error sinks).

3) Calibrate assets and attacker capabilities

  • List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).
  • Describe realistic attacker capabilities based on exposure and intended usage.
  • Explicitly note non-capabilities to avoid inflated severity.

4) Enumerate threats as abuse paths

  • Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).
  • Classify each threat and tie it to impacted assets.
  • Keep the number of threats small but high quality.

5) Prioritize with explicit likelihood and impact reasoning

  • Use qualitative likelihood and impact (low/medium/high) with short justifications.
  • Set overall priority (critical/high/medium/low) using likelihood x impact, adjusted for existing controls.
  • State which assumptions most influence the ranking.

6) Validate service context and assumptions with the user

  • Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.
  • Ask 1–3 targeted questions to resolve missing context (service owner and environment, scale/users, deployment model, authn/authz, internet exposure, data sensitivity, multi-tenancy).
  • Pause and wait for user feedback before producing the final report.
  • If the user declines or can’t answer, state which assumptions remain and how they influence priority.

7) Recommend mitigations and focus paths

  • Distinguish existing mitigations (with evidence) from recommended mitigations.
  • Tie mitigations to concrete locations (component, boundary, or entry point) and control types (authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging).
  • Prefer specific implementation hints over generic advice (e.g., "enforce schema at gateway for upload payloads" vs "validate inputs").
  • Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.

8) Run a quality check before finalizing

  • Confirm all discovered entrypoints are covered.
  • Confirm each trust boundary is represented in threats.
  • Confirm runtime vs CI/dev separation.
  • Confirm user clarifications (or explicit non-responses) are reflected.
  • Confirm assumptions and open questions are explicit.
  • Confirm that the format of the report matches closely the required output format defined in prompt template: references/prompt-template.md
  • Write the final Markdown to a file named -threat-model.md (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).

Risk prioritization guidance (illustrative, not exhaustive)

  • High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.
  • Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log/metrics poisoning that affects detection.
  • Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.

References

  • Output contract and full prompt template: references/prompt-template.md
  • Optional controls/asset list: references/security-controls-and-assets.md

Only load the reference files you need. Keep the final result concise, grounded, and reviewable.

Questions people ask

Does it produce a generic OWASP-style checklist?
No. The workflow explicitly prioritizes realistic attacker goals and concrete impacts over generic checklists, and requires each architectural claim to be anchored to evidence in the repository.
What does it need from me before it starts?
Ideally the repo root and in-scope paths, plus intended usage, deployment model, internet exposure, and auth expectations. It can infer some of this, but it pauses mid-workflow to ask 1–3 targeted questions and waits for your answers before the final report.
What is the output?
A single Markdown file named `-threat-model.md`, using the basename of the repo root or the in-scope directory, written to match the output contract in references/prompt-template.md.
Will it flag things it cannot verify?
Yes. Assumptions and open questions must be stated explicitly, existing mitigations are distinguished from recommended ones with evidence, and if you decline to answer its questions it records which assumptions remain and how they affect priority.

Related skills

Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.

by johnpatternai22 installs8 stars

docx

Official

Create, edit, read, and redline .docx and .dotx files, then render the result to check it visually.

by Anthropic197.6k stars

pdf

Official

Read, merge, split, rotate, watermark, encrypt, and create PDFs with Python and CLI recipes.

by Anthropic197.6k stars

chatgpt-apps

Official

Scaffold, refactor, and troubleshoot ChatGPT Apps SDK apps built from an MCP server plus a widget UI.

by OpenAI28.8k stars

Build or update full Figma screens using your published design system's components, variables, and styles.

by OpenAI28.8k stars

More from OpenAI

Browse all skills

chatgpt-apps

Official

Scaffold, refactor, and troubleshoot ChatGPT Apps SDK apps built from an MCP server plus a widget UI.

by OpenAI28.8k stars

Build or update full Figma screens using your published design system's components, variables, and styles.

by OpenAI28.8k stars

Build a Figma design system from your codebase through phased, checkpoint-gated steps.

by OpenAI28.8k stars

figma-use

Official

Run JavaScript against the Figma Plugin API to create, edit, and inspect nodes in a Figma file.

by OpenAI28.8k stars

hatch-pet

Official

Turn a concept, brand cue, or reference image into a validated 8x9 animated Codex pet atlas with QA sheets and pet.json packaging.

by OpenAI28.8k stars

imagegen

Official

Generate or edit raster images in your project, from hero shots and sprites to transparent-background cutouts.

by OpenAI28.8k stars