Agent skill · security · davila7
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. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Why this skill is useful
Adds a structured threat modeling process with specific steps and outputs that enhance the AI's ability to perform AppSec assessments.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
Threat Model Source Code Repo 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. Quick start 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. Workflow 1) Scope and extract the system model Identify primary components, data stores, and external integrations from the repo summary. Identify how the system runs (server, CLI, library, worker) and its entrypoints. Separate runtime behavior from CI/build/dev tooling and from tests/examples. Map the in-scope locations to those components and exclude out-of-scope items explicitly. Do not claim components, flows, or controls without evidence. 2) Derive boundaries, assets, and entry points Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting. List assets that drive risk (data, credentials, models, config, compute resources, audit logs). Identify entry points (endpoints, upload surfaces, parsers/decoders, job triggers, admin tooling, logging/error sinks). 3) Calibrate assets and attacker capabilities List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts). Describe realistic attacker capabilities based on exposure and intended usage. Explicitly note non-capabilities to avoid inflated severity. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/security-threat-model