Threat Model

What it does

When your agent uses it

• Security review
• Trust boundaries
• Assessing a projects security posture
• The user is about to build security-sensitive features (auth

Example prompts

• “threat model”
• “security review”
• “attack surface”
• “/threat-model”

Requirements

• A Bash shell

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Read methodology for the detailed approach at each phase
2. 2Read output format for the document structure (6 sections)
3. 3Consult attack patterns for technology-specific patterns
4. 4Run scripts/trace-data-flows.sh to inventory entry points and sinks
5. 5Optionally run scripts/scan-patterns.sh for security-relevant code patterns

What it can do on your machine

Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 2 files in scripts/ (Shell), which the agent can run.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Threat Model loads about 1.7k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 144 tokens; SKILL.md has 550 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~144

When it runs · the whole SKILL.md, loaded when a task matches

~1.7k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~18k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 550 words, ~1,686 tokens.

name

threat-model

description

Security threat modeling, attack surface mapping, and trust boundary analysis on a codebase. Triggers on 'threat model', 'security review', 'attack surface', 'trust boundaries', or when assessing a project's security posture. Also trigger when the user is about to build security-sensitive features (auth, crypto, file I/O, network services, native bridges) and needs to understand the threat landscape first — even if they don't explicitly say "threat model." Also triggers on 'what changed' or 'diff analysis' for incremental security review of recent commits.

Phase 0 (conditional): Diff Analysis — if git range provided, scope to changed code
Phase 1:  Codebase Survey        → Understand what the project is and does
Phase 2:  Component Mapping      → Identify components, data flows, and language bridges
Phase 3:  Asset Identification   → Determine what needs protecting
Phase 4:  Trust Boundaries       → Classify inputs by trust level, inventory entry points
Phase 5:  Data Flow Tracing      → Follow untrusted values from entry to sink ← key technique
Phase 6:  Attack Surface Enum    → Document surfaces with traced evidence
Phase 7:  Pattern Clustering     → Group 3+ similar findings by root cause
Phase 8:  Exploit Chains         → Combine findings into multi-step attack paths
Phase 9:  Calibration            → Rate with chain-adjusted and systemic severity
Phase 10: Output                 → Write structured THREAT-MODEL.md

threat-model → findings.json → threat-patch (consumes findings, generates fixes)
     ↑                                          ↓
     └── threat-model --diff (re-analyzes, updates finding status) ←── git commits

© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files (scripts, references) in skills/.experimental/threat-model of pproenca/dot-skills.

• SKILL.md
• config.json
• gotchas.md
• metadata.json
• references/attack-patterns.md
• references/findings-schema.md
• references/methodology.md
• references/output-format.md
• references/techniques/bridge-analysis.md
• references/techniques/data-flow-tracing.md
• references/techniques/diff-analysis.md
• references/techniques/exploit-chains.md
• references/techniques/pattern-clustering.md
• scripts/scan-patterns.sh
• scripts/trace-data-flows.sh

Open the folder on GitHubat commit cf93c57