TM Security Review (comprehensive tier)

Model first, hunt second. A bare hunt enumerates source→sink flows but never asks "is this source actually lower-trust than its sink?" — so it over-rates operator-controlled inputs (CLI flags, config, a JAR on the classpath) as HIGH and misses the real design risk (e.g. an indirect-prompt-injection → auto-exec chain). The threat model supplies that missing trust-direction check. This skill builds the model, then runs the sophisticated zeroday exploit hunt against it.

This is the deep, comprehensive, whole-repo review with a threat model as input — the heavier of the two tiers. When you only need a quick pass over the changes on a branch/worktree, use tm-quick-security-assessment instead (and optionally hand its finding surface here for the deep follow-up).

It composes two sibling skills:

• Phase 0 → threat-modeling (../threat-modeling/SKILL.md) — STRIDE/DREAD, DFD, trust boundaries.
• Phases 1-3 → 0day-scanner (../0day-scanner/SKILL.md) — the LLM exploit engine, run in deep mode, steered by the model's KEY threats. Its on-disk fallback (security-reviewer/languages/* + 8-point check) applies when the MCP tool is unreachable.