Security Threat Model
Threat-model the user's own app from its real code. Draws the data flow (actors, trust boundaries, data stores, external services) as a Mermaid diagram, finds threats per element with STRIDE, ranks them by likelihood times impact, then proves each top risk with a local failing test, fixes it, and keeps the test as a regression test. Covers auth, IDOR and tenant isolation, injection, SSRF, secrets, CORS/CSRF, uploads, webhooks, dependencies, abuse, and LLM-app risks like prompt injection through tool output. Writes THREAT_MODEL.md. Use when the user says "threat model", "security review of my a
Install
npx skills add dotslashsimran/simcraft --skill security-threat-modelgit clone --depth 1 https://github.com/dotslashsimran/simcraft.git /tmp/simcraft
mkdir -p ~/.claude/skills
cp -r /tmp/simcraft/skills/coding/security-threat-model ~/.claude/skills/security-threat-modelPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Security threat model The goal is not a long list of everything that could go wrong. It is the three to six things that would actually hurt, proven real on the user's own machine, fixed, and locked in with tests. A threat without a proof is a guess. A fix without a regression test comes back in six months. Only for code and systems the user owns. Every proof runs against local code or a local dev server with throwaway data. Never send a proof to production, a staging server shared with others, or any third-party service, even one the app calls. ## 1. Scope (ask, one question at a time) - What does the app do, who uses it, and what would be bad news (leaked data, lost money, someone else's account, a big bill)? - What is in scope (which repo, which services) and how does it run locally? - How is it deployed (behind a proxy, serverless, single box)? This decides which threats are the app's job. Write the answers at the top of `THREAT_MODEL.md`. ## 2. Map the surface from the code ``` python3 ~/simcraft/skills/coding/security-threat-model/scripts/surface.py <repo> python3 ~/simcraft/skills/coding/security-threat-model/scripts/secrets_scan.py <repo> --history ```
Details
- Skill name
security-threat-model- Repository
- dotslashsimran/simcraft
- Path
skills/coding/security-threat-model/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Security Threat Model skill do?
Threat-model the user's own app from its real code. Draws the data flow (actors, trust boundaries, data stores, external services) as a Mermaid diagram, finds threats per element with STRIDE, ranks them by likelihood times impact, then proves each top risk with a local failing test, fixes it, and keeps the test as a regression test. Covers auth, IDOR and tenant isolation, injection, SSRF, secrets, CORS/CSRF, uploads, webhooks, dependencies, abuse, and LLM-app risks like prompt injection through tool output. Writes THREAT_MODEL.md. Use when the user says "threat model", "security review of my a
How do I install the Security Threat Model skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add dotslashsimran/simcraft --skill security-threat-model. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Security Threat Model popular?
It lives in dotslashsimran/simcraft, which has 517 GitHub stars and 39 forks.
Related skills
API Design Review
517dotslashsimran/simcraft
Review the design of an API surface, meaning an HTTP API (OpenAPI spec or route code), an SDK's public classes and functions, or a CLI. Checks naming and consistency, resource modelling, error design (stable codes, RFC 9457 problem details, request ids), versioning and breaking changes, pagination, filtering, idempotency and retries, rate limits, timeouts, long-running operations, webhooks, auth, partial updates, ID, time and money formats, SDK ergonomics and CLI conventions. Uses scripts to lint OpenAPI files, classify changes between two spec versions as breaking or safe, and dump an SDK's p
Benchmark Honestly
517dotslashsimran/simcraft
Build benchmarks that survive scrutiny and catch the classic lies (dead code elimination, lazy results, constant folding, warm caches, coordinated omission, averages hiding GC pauses, unequal work, noisy machines). Defines the question first, controls and discloses the environment, uses warmups, interleaved repeats, medians, bootstrap confidence intervals and Mann-Whitney tests, and ends with a one-line verdict that includes the CI. Bundles a command runner, an environment reporter and an open-loop latency tester. Use when the user says "benchmark this", "is this faster", "compare performance"
Bisect Anything
517dotslashsimran/simcraft
Find the exact commit (or dependency version, config value, or input) that caused a regression by turning it into an automatic pass/fail check and running git bisect run in a separate worktree, then shrink the bad commit to the hunk that matters and explain it. Handles failing tests, changed output, slowdowns, crashes, visual changes, server behaviour, flaky checks, unbuildable commits and merge-heavy history. Use when the user says "what broke this", "find the commit that", "when did this start", "it used to work", "regression", "git bisect", "which version broke it", or "which change made it
Security Monitoring
581claude-office-skills/skills
Automate security monitoring, threat detection, incident response, and compliance workflows
Skill Security Auditor
151mar-antaya/my-claude-skills
Security audit and vulnerability scanner for AI agent skills before installation. Use when: (1) evaluating a skill from an untrusted source, (2) auditing a skill directory or git repo URL for malicious code, (3) pre-install security gate for Claude Code plugins, OpenClaw skills, or Codex skills, (4) scanning Python scripts for dangerous patterns like os.system, eval, subprocess, network exfiltration, (5) detecting prompt injection in SKILL.md files, (6) checking dependency supply chain risks, (7) verifying file system access stays within skill boundaries. Triggers: "audit this skill", "is this
K8S Security Policies
514Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or enforcing pod security standards.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.