Security Ownership and Bus-Factor Analysis
Use Git history to map people to sensitive files, inspect ownership concentration and export CSV or graph data for security-focused reposito…
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.
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.
references/prompt-template.md<repo-or-dir-name>-threat-model.md (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).references/prompt-template.mdreferences/security-controls-and-assets.mdOnly load the reference files you need. Keep the final result concise, grounded, and reviewable.
Source: openai · Apache-2.0 · SHA-256 shown alongside the download.
License file included. A license and checksum are not a security certification. Review package instructions and scripts before running them.
openai-security-threat-model/LICENSE.txt10776 bytesopenai-security-threat-model/SKILL.md5680 bytesAn adaptation record is bundled. Inspect the declared changes and archived original before use. Review adaptation and original-file hashes →
Machine-readable installation guide →Records are supplied by the site administrator and bound to a specific package. They are not third-party safety certification. This page does not execute skills.
No published scenario records yet. Resource availability and download counts do not imply measured task performance.
Be the first to share your experience.
Sign in to leave a review →Links use published guide associations and catalog labels. Inspect each resource’s requirements and license.
Use Git history to map people to sensitive files, inspect ownership concentration and export CSV or graph data for security-focused reposito…
Review Python, JavaScript, TypeScript or Go code against framework-specific security practices when a security review or hardening task is e…
Turn recorded speech into text, with optional speaker labels and known-speaker hints. Inspect the transcription script and API requirements …
Generate spoken narration or batches of audio from supplied text using the bundled speech script. Live calls require an API key; custom voic…