security-threat-model
OfficialRepository-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 use
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
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.
Automated safety checks
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
- Scanned
- 5 files, 371 lines
About this skill
What it does
This skill generates comprehensive security threat models based on provided repository context. It automatically identifies trust boundaries, critical assets within a system, potential attacker capabilities, possible abuse pathways, and suggests corresponding mitigation strategies. The output is formatted as a concise Markdown document, facilitating easy review and integration into existing documentation.
When to use it
- New Project Planning: Generate an initial threat model during the design phase of a new software project to proactively identify potential security risks.
- Codebase Review: Analyze an existing codebase to uncover vulnerabilities and weaknesses that might be exploited by attackers.
- Security Audits: Supplement manual security audits with automated threat modeling for broader coverage and faster analysis.
- Risk Assessment: Quickly assess the overall security posture of a system or application based on identified threats and mitigations.
Key capabilities
- Enumerates trust boundaries within a repository.
- Identifies critical assets requiring protection.
- Lists potential attacker capabilities.
- Maps abuse paths detailing how attackers might exploit vulnerabilities.
- Proposes mitigation strategies to address identified risks.
- Generates Markdown formatted threat model output.
Example prompts
- "Generate a threat model for this repository: [repository URL]"
- "Threat model the following code, focusing on potential data leakage: [code snippet]"
- “Create a security threat model for the authentication module in this project.”
Tips & gotchas
The skill's effectiveness is directly tied to the quality and completeness of the repository context provided. Ensure the input repository accurately reflects the system being analyzed for optimal results.