Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Source reviewedSecurity reviewExplored

OpenAI / skills/.curated/security-threat-model/SKILL.md

Security Threat Model

Writes a repository-specific threat model: trust boundaries, assets, abuse paths and mitigations tied to evidence in the code.

Source reviewed · reviewed · Named sources were inspected. No runtime results are established by this label.

01 / Task fit

Where it may help.

These are intended uses indicated by the upstream material. They are not measured outcomes.

  • Pre-launch review of apps that handle data or credentials
  • Focused threat lists tied to the actual code

What it is

This skill walks an agent through threat modeling a codebase. It maps components and entry points, lists the assets that matter, describes realistic attackers and ranks a small number of abuse paths by likelihood and impact. It must check its assumptions with you before writing the final report, which it saves as a Markdown file.

Why you might use it

Use it before launching an app or integration that handles customer data or credentials, when you want a focused list of what could go wrong rather than a generic checklist. It's a review aid, not an audit or penetration test.

Put it in context.

Illustrative requests and outputs to review. These examples are separate from the recorded evaluation below.

Model a small web app

Example request

Threat model this repository. It is a booking app with a public form and an admin page. Ask me about deployment before you rank anything.

What to look for. A Markdown threat model with boundaries, assets, ranked threats and mitigations, after a short round of questions.

Before you rely on it. Rankings depend on the answers you give. A wrong assumption about who can reach the admin page changes the result.

Check an integration path

Example request

Threat model only the webhooks/ folder, which receives payment events.

What to look for. A scoped model of the webhook entry point and its trust boundary.

Before you rely on it. A scoped model doesn't cover the rest of the system. Note what was left out.

02 / Setup & access

What it asks of your environment.

Requirements

  • An agent with read access to the repository, and a person who can answer questions about deployment and users.
  • No account or service is needed to read the code.

Permissions & data access

  • Reads repository files in scope.
  • Writes one Markdown threat-model file.
Check the host, too.

Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.

03 / Things to check

Security concerns & practical limits.

These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.

Review before use

Not a security assurance

The output is a model built from code reading and your answers. It doesn't test anything. Treat high-priority items as things to verify, not as findings.

Limits and nuances

  • Source review of SKILL.md and the per-skill license only. The reference prompt template and controls list were not reviewed.
  • No repository was modeled. No accuracy or coverage result is claimed.

04 / Review record

What we checked. What’s still open.

Source reviewed

Recorded review scope

  • skills/.curated/security-threat-model/SKILL.md
  • skills/.curated/security-threat-model/LICENSE.txt
Not verified

Not tested or established

  • Source review of SKILL.md and the per-skill license only. The reference prompt template and controls list were not reviewed.
  • No repository was modeled. No accuracy or coverage result is claimed.
Review date
Source revision
49f948faa9258a0c61caceaf225e179651397431
Our relationship
Explored. Investigated through the recorded review. No use or replication is claimed.

Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.

Recorded evaluation / Source review

Results with their limits attached.

Completed within scope

Completed 4 bounded source checks on the pinned entrypoint and license. No skill workflow was executed.

Passed
4
Failed
0
Total recorded
4

These counts refer to the cases in this report. They are not a benchmark against other skills. A source review does not establish runtime behavior.

Read the evidence report

The report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.

Recorded environment

  • Pinned public UTF-8 sources fetched from raw.githubusercontent.com at the recorded commit and hashed with SHA-256.
  • Linux; Python 3.13.5 source-condition check. No account, credentials, private documents or live business data.
Recorded commands (2)

Commands document this evaluation. They are not setup instructions for your environment.

Read each pinned file listed in sourceManifest.
python3 r6_skills.py: check each recorded source condition and reconcile report counts.

Findings from this evaluation

Needs attention

Not a security assurance

The output is a model built from code reading and your answers. It doesn't test anything. Treat high-priority items as things to verify, not as findings.

Observation

Pauses for your input

The workflow stops to confirm assumptions before producing the final report.

Evaluation limitations

  • Source review of SKILL.md and the per-skill license only. The reference prompt template and controls list were not reviewed.
  • No repository was modeled. No accuracy or coverage result is claimed.

05 / Reuse & discovery

License, attribution & popularity.

Apache-2.0

Apache-2.0 license text inspected at this revision. Keep the license and any NOTICE when redistributing covered files. The services and accounts the skill uses have their own terms.

Why it is in this collection

GitHub displayed 28,155 stars for the openai/skills repository on the observation date. Repository-wide; not individual skill usage, quality or safety.

28,155 repository stars

Scope
Entire openai/skills repository, not this individual skill
Observed
Time window
Snapshot observed 2026-10-19
Discovery source ↗

Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.

06 / Follow the evidence

Go to the original.

  1. Pinned skill instructions github.com
  2. Pinned license github.com
  3. Repository (dated star count) github.com

IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.