threat-model SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
threat-model from byerlikaya/claude-starter-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add byerlikaya/claude-starter-kit/threat-model@git:20260926.aaa5dbcPins git:20260926.aaa5dbc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- byerlikaya/claude-starter-kit
- Path
kit/skills/threat-model/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260926.aaa5dbc, committed Sep 26, 2026
- First version recorded
- Sep 24, 2026
- Size
- 3,470 bytes
- Repository stars
- 25
- License
- MIT
Scope a security audit BEFORE scanning, to cut false positives: map assets, entry points, trust boundaries and 5-8 domain-specific attack classes into a parseable THREAT_MODEL.md. A threat survives a patch; a vulnerability is only evidence for one. Feeds security-scan.
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
# Threat Model <!-- routing-eval reads the next line; why it sits in the body: AGENT_TEMPLATE.md --> Trigger phrases: "threat model", "attack surface", "scope the audit", "trust boundary" Scope first, scan second. A security scan with no map produces noise; a threat model tells the scanner (and `security-scan`) **where to look and what matters** — the single biggest lever on false positives. The one idea to keep — the litmus test: **if patching one line of code makes an entry disappear, it was a vulnerability, not a threat.** Threats survive patching (they name *what an attacker wants and the surface they arrive through*); a vulnerability is only **evidence** that raises a threat's likelihood. > **Crewforth adaptation (local, .claude/):** `crew-security-expert` runs this to scope before `security-scan`. Output > `docs/THREAT_MODEL.md` is internal (§4.3). Stack-agnostic. §4 Prohibitions apply. ## When - Before a first `security-scan` of a system, or when scan output is noisy / unscoped. - After a significant new surface — a new API, a new integration, a new trust boundary. ## Two modes - **interview** — the owner is available: ask the four questions below, one at a time. …
Read the whole file at its exact version.
How to install
mdr add byerlikaya/claude-starter-kit/threat-model@sha256:38a4afbf6d35b6ddThe line at the top of this page pins the label git:20260926.aaa5dbc, 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_q4aerrp7ep7vnqck)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 24, 2026 and Sep 26, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.aaa5dbc latest | 2026-09-26 | aaa5dbc | 3,470 B | A | view · diff |
| git:20260924.a457823 | 2026-09-24 | a457823 | 3,464 B | A | view · diff |
| git:20260924.ccb2bc9 | 2026-09-24 | ccb2bc9 | 3,658 B | A | view · diff |
| git:20260924.bd59e95 | 2026-09-24 | bd59e95 | 3,658 B | A | view · diff |
| git:20260924.ad81b1a | 2026-09-24 | ad81b1a | 3,657 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 (3470 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
byerlikaya/claude-starter-kit · 25 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q4aerrp7ep7vnqck GET https://markdownregistry.com/api/v1/resolve?ref=byerlikaya/claude-starter-kit/threat-model GET https://markdownregistry.com/api/v1/blob/38a4afbf6d35b6ddb6f8d8e494bb66a1f525d6038f5ebf1b1af18fe13101cc3d
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.
More from byerlikaya/claude-starter-kit
Every file in byerlikaya/claude-starter-kit