Kjell Tore Guttormsen
3b034d9266
Hver /security <cmd> som produserer rapport printer nå en klikkbar file://-lenke til en self-contained HTML-versjon. Levert over fem sesjoner; sesjon 5 wirer de 14 resterende skill-filene + slipper v7.7.0 (versjonsbump + docs). Sesjon-historikk: - Sesjon 1 (0dc7ff4) — playground katalog list-view + builder-pane med copy-knapp på alle 18 rapporter - Sesjon 2 (86d6ecd) — playground prosjekt-surface opprydding (stub-screen + topbar-splitt) - Sesjon 3 (fa5fb48) — extract 18 inline parsers + 18 inline renderers fra playground til canonical ESM-modul scripts/lib/report-renderers.mjs (playground beholder bit-identisk inline-kopi siden ESM import ikke fungerer fra file://) - Sesjon 4 (db80854) — ny zero-dep CLI scripts/render-report.mjs (stdin/file/stdout-modus, kebab→camel commandId-routing, ~140 KB self-contained HTML med 6 inlined DS-stylesheets + lokal .report-table, absolutte file://-paths for Ghostty cmd-click). 4 skills wired: scan, audit, posture, deep-scan. - Sesjon 5 (denne) — 14 resterende skills wired: plugin-audit, mcp-audit, mcp-inspect, ide-scan, supply-check, dashboard, pre-deploy, diff, watch, registry, clean, harden, threat-model, red-team. Hver skill-fil har nå en HTML Report-step som instruerer Claude å skrive markdown verbatim, kjøre CLI, og appende klikkbar file://-lenke til respons. Release-arbeid: - Versjonsbump v7.6.1 → v7.7.0 i 6 plugin-filer + 2 rot-filer (package.json, .claude-plugin/plugin.json, README badge, CLAUDE.md header + state-seksjon, docs/version-history.md, plugin Recent versions- tabell, rot README plugin-entry, rot CLAUDE.md plugin-katalog) - CHANGELOG [7.7.0] med full historikk fra sesjon 1-5 - docs/version-history.md v7.7.0-seksjon Verifisert: - 18/18 commandIds i CLI gir > 138 KB self-contained HTML - 1819/1820 tester grønne (pre-compact-scan-perf-flake fyrte under last, passerer i isolasjon på 1582 ms — pre-eksisterende, defer til v7.7.x) - 18/18 skill-filer har HTML Report-step - Ingen kildefil-treff på 7.6.1 utenfor historiske changelog/version- history/README releases-tabell Ingen scanner- eller hook-atferdsendringer — purely additive surface. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
47 lines
2.1 KiB
Markdown
47 lines
2.1 KiB
Markdown
---
|
||
name: security:threat-model
|
||
description: Interactive threat modeling using STRIDE and MAESTRO frameworks — guides architecture analysis and generates threat model document
|
||
allowed-tools: Read, Glob, Grep, AskUserQuestion, Agent
|
||
model: sonnet
|
||
---
|
||
|
||
# /security threat-model
|
||
|
||
Interactive threat modeling — STRIDE x MAESTRO, 5-phase interview, complete threat model document.
|
||
|
||
## Run Session
|
||
|
||
Spawn `subagent_type: "llm-security:threat-modeler-agent"`, `model: "opus"`:
|
||
|
||
> Run the full 5-phase interactive threat modeling session.
|
||
> Read these knowledge files (absolute paths):
|
||
> - \<plugin-root\>/knowledge/skill-threat-patterns.md
|
||
> - \<plugin-root\>/knowledge/mcp-threat-patterns.md
|
||
> Follow your interview workflow: Architecture Discovery → Component Mapping → Threat Identification (STRIDE x MAESTRO) → Risk Assessment → Mitigation Mapping.
|
||
> Output the complete threat model document directly to the conversation.
|
||
|
||
## After Session
|
||
|
||
- To save: ask user if they want it written to `threat-model.md`
|
||
- To verify mitigations: `/security posture`
|
||
- For production readiness: `/security pre-deploy`
|
||
|
||
## HTML Report
|
||
|
||
After the threat-modeler agent has produced the complete threat-model markdown document:
|
||
|
||
1. Compute a temp markdown path:
|
||
```bash
|
||
node -p "require('path').join(require('os').tmpdir(), 'sec-threat-model-' + Date.now() + '.md')"
|
||
```
|
||
2. Use the Write tool to save the **entire threat-model markdown you just produced** (Architecture Discovery + Component Mapping + STRIDE × MAESTRO threat matrix + Risk Assessment + Mitigation Mapping) to that temp path. Verbatim.
|
||
3. Run the renderer:
|
||
```bash
|
||
node <plugin-root>/scripts/render-report.mjs threat-model --in "<temp-md-path>"
|
||
```
|
||
The CLI writes `reports/threat-model-<YYYYMMDD-HHmmss>.html` relative to CWD and prints `file:///abs/path.html` on stdout.
|
||
4. Append to your response (markdown link, no bare URL):
|
||
|
||
> **HTML-rapport:** [Åpne i nettleser](file:///abs/path.html)
|
||
|
||
If the CLI exits non-zero, mention the error but do not block — the markdown threat-model document above is the primary deliverable.
|