skilld
All skills
openai avatar

/security-threat-model

@5c8f1e2 official
by openaiopenai/skills28k stars
1,891

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/security-threat-model

This session only. Nothing lands on disk.

referencessecurity-controls-and-assets.md

≈420 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Security Controls and Asset Categories

Use this as a lightweight checklist to keep outputs consistent across teams. Prefer concrete, system-specific items over generic text.

Asset categories (pick only what applies)

  • User data (PII, content, uploads)
  • Authentication artifacts (passwords, tokens, sessions, cookies)
  • Authorization state (roles, policies, ACLs)
  • Secrets and keys (API keys, signing keys, encryption keys)
  • Configuration and feature flags
  • Models and weights (if ML systems)
  • Source code and build artifacts
  • Audit logs and telemetry
  • Availability-critical resources (queues, caches, rate limits, compute budgets)
  • Tenant isolation boundaries and metadata

Security control categories

  • Identity and access: authN, authZ, session handling, mTLS, key rotation
  • Input protection: schema validation, parsing hardening, upload scanning, sandboxing
  • Network safeguards: TLS, network policies, WAF, rate limiting, DoS controls
  • Data protection: encryption at rest/in transit, tokenization, redaction
  • Isolation: process sandboxing, container boundaries, tenant isolation, seccomp
  • Observability: audit logs, alerting, anomaly detection, tamper resistance
  • Supply chain: dependency pinning, SBOMs, provenance, signing
  • Change control: CI checks, deployment approvals, config guardrails

Mitigation phrasing patterns

  • "Enforce schema at <boundary> for <payload> before <component>."
  • "Require authZ check for <action> on <resource> in <service>."
  • "Isolate <parser/component> in a sandbox with <resource limits>."
  • "Rate limit <endpoint> by <key> and apply burst caps."
  • "Encrypt <data> at rest using <key management> and rotate <keys>."

Source: SKILL.md on GitHub

Third-party checks

1 warning17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill provides a structured framework for performing security threat modeling on a codebase. It facilitates the identification of trust boundaries, assets, and potential abuse paths through repository analysis. The skill includes defensive instructions, such as redacting secrets and grounding all security claims in repository evidence, which align with security best practices.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    5/5 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 5c8f1e2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 8 months ago

Topics

  • Security
  • threat-modeling
  • appsec
  • architecture
  • risk-assessment
  • vulnerability-analysis
  • trust-boundaries
  • compliance

README badge

README badge for openai/skills/security-threat-model

What it does

Enumerates trust boundaries, assets, entry points, and realistic abuse paths in a codebase, then writes a prioritized AppSec threat model in Markdown. Targets explicit threat modeling requests — not general code review or architecture design work.

Generated from the current SKILL.md.

Frequently asked

Does this skill work on any codebase, or only specific frameworks?
It works on any codebase. The skill extracts the system model from the repository structure and code evidence, then derives threats based on actual components, boundaries, and entry points—not framework-specific templates.
When should I trigger this skill?
Trigger only when you explicitly ask for threat modeling, abuse path enumeration, or AppSec analysis of a codebase or path. Do not trigger for general architecture summaries, code review, or non-security design discussions.
Does this skill require me to provide deployment or auth details upfront?
No. The skill infers intended usage and deployment from the repository, but pauses at step 6 to validate key assumptions (service owner, environment, scale, authn/authz model, internet exposure, data sensitivity) with you before finalizing the threat model.
What does the final output look like?
A concise Markdown threat model file named after the repo or directory, containing scoped components, trust boundaries, assets, entry points, prioritized threats with likelihood and impact reasoning, and concrete mitigation recommendations tied to specific locations in the codebase.
Does this skill enumerate generic security checklists?
No. Every architectural claim, threat, and mitigation is grounded in evidence from the actual repository. Generic checklist items without repository context are excluded.

Generated from the current SKILL.md. These answers refresh after source changes.