security-threat-model

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Use when the user asks to threat model a codebase or path, enumerate threats or abuse paths, or perform AppSec threat modeling. Do NOT use for general architecture summaries, code review, security best practices (use security-best-practices), or non-security design work.

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-changelog-update 456,653 ★
  Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified cont
• git-guardrails-claude-code 323,485 ★
  Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before t
• pr 323,485 ★
  Use when writing a PR body.
• setup-matt-pocock-skills 323,485 ★
  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain
• setup-pre-commit 323,485 ★
  Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use w