sota-threat-modeling SKILL.md skillA
sota-threat-modeling from martinholovsky/sota-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add martinholovsky/sota-skills/sota-threat-modeling@git:20261026.808c340Pins git:20261026.808c340 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- martinholovsky/sota-skills
- Path
skills/sota-threat-modeling/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261026.808c340, committed Oct 26, 2026
- First version recorded
- Jun 17, 2026
- Size
- 10,615 bytes
- Repository stars
- 26
- License
- CC-BY-4.0
State-of-the-art threat modeling for both designing new systems and auditing existing ones. Use when designing a feature, service, integration, or architecture that touches untrusted input, new trust boundaries, sensitive data, or third-party dependencies (BUILD mode), and when reviewing, auditing, or pen-test-scoping an existing codebase to reconstruct its implicit threat model and find gaps (AUDIT mode). Not for code-level vulnerability review — use sota-code-security. Trigger keywords…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SOTA Threat Modeling ## Purpose Threat modeling answers Shostack's four questions with engineering rigor: 1. **What are we working on?** (decompose: DFD, trust boundaries, assets, actors) 2. **What can go wrong?** (enumerate: STRIDE/LINDDUN per element, catalogs, attack trees) 3. **What are we going to do about it?** (treat: mitigate/accept/transfer/avoid, map to requirements and tests) 4. **Did we do a good job?** (verify: abuse-case tests, residual risk review, re-model triggers) This skill operationalizes those questions in two modes. Never produce a threat model that is only prose — every threat must land as a tracked requirement, a test, or an explicitly accepted risk with an owner. ## BUILD Mode — Threat-Model-While-Designing Run this workflow whenever designing anything that crosses a trust boundary. Scale effort to risk: a 15-minute "four questions" pass for a small feature; a full STRIDE-per-interaction model for a new service or auth flow. ### Workflow 1. **Scope the delta.** Model what is new or changed, not the whole system. List new entry points, new data classes, new dependencies, new actors. …
Read the whole file at its exact version.
How to install
mdr add martinholovsky/sota-skills/sota-threat-modeling@sha256:27d5d0043b357231The line at the top of this page pins the label git:20261026.808c340, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jki6uiylmt7g3pyx)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Jun 17, 2026 and Oct 26, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.808c340 latest | 2026-10-26 | 808c340 | 10,615 B | A | view · diff |
| git:20261025.c05557f | 2026-10-25 | c05557f | 10,494 B | A | view · diff |
| git:20261024.8dd2b0a | 2026-10-24 | 8dd2b0a | 10,334 B | A | view · diff |
| git:20261012.ae1b29b | 2026-10-12 | ae1b29b | 10,093 B | A | view · diff |
| git:20261002.3e41957 | 2026-10-02 | 3e41957 | 9,487 B | A | view · diff |
| git:20260925.f714894 | 2026-09-25 | f714894 | 9,348 B | A | view · diff |
| git:20260716.e4afc80 | 2026-07-16 | e4afc80 | 9,281 B | A | view · diff |
| git:20260617.c5d2c7b | 2026-06-17 | c5d2c7b | 9,211 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10615 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
martinholovsky/sota-skills · 26 stars · license CC-BY-4.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jki6uiylmt7g3pyx GET https://markdownregistry.com/api/v1/resolve?ref=martinholovsky/sota-skills/sota-threat-modeling GET https://markdownregistry.com/api/v1/blob/27d5d0043b3572318c089b8b58feea7cae29ad9cdf63c9863f66a9c50710d70e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.