Skip to content
TrustedSkillsbeta
Back to all skills

Security Threat Model

Official
openai·vlatest·security

Official openai skill covering security, data modeling for implementing security and authentication.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add openai/skills --skill security-threat-model -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

openai

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned openai/skills at 49f948faa9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
49f948faa9
Manifest
skills/.curated/security-threat-model/SKILL.md
Scanned
5 files, 371 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The security-threat-model skill enables AI agents to identify, analyze, and mitigate potential security threats within a system or application. It leverages known threat modeling methodologies to assess vulnerabilities, evaluate risk levels, and suggest countermeasures based on the context provided.

When to use it

  • Before deploying a new software system to proactively identify possible attack vectors.
  • During a security audit to systematically review an existing infrastructure for weaknesses.
  • When designing secure APIs or microservices to ensure robustness against common threats like injection attacks or data leaks.
  • In response to a security incident to understand the root cause and prevent future occurrences.

Key capabilities

  • Identifies potential threat vectors using established frameworks.
  • Assesses risk levels based on impact and likelihood of exploitation.
  • Suggests mitigation strategies tailored to specific scenarios.
  • Supports both high-level architectural reviews and granular code-level analysis.

Example prompts

  • "Analyze the security risks in this web application architecture."
  • "What are common threats for a payment processing API, and how can they be mitigated?"
  • "Generate a threat model for a cloud-based user authentication system."

Tips & gotchas

  • Provide as much context as possible (e.g., system components, data flows) to ensure accurate modeling.
  • Use in conjunction with other security tools like vulnerability scanners for comprehensive coverage.