diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 0dfb850..7018cb4 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,5 +1,5 @@
 {
   "name": "llm-security",
   "description": "Security scanning, auditing, and threat modeling for Claude Code projects. Detects secrets, validates MCP servers, assesses security posture, and generates threat models aligned with OWASP LLM Top 10.",
-  "version": "7.6.1"
+  "version": "7.7.0"
 }
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4a4099c..a3dfb52 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,71 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [7.7.0] - 2026-05-18
+
+HTML-rapport for alle 18 skill-kommandoer som produserer rapport.
+Hver `/security <cmd>` printer nå en klikkbar `file://`-lenke til en
+self-contained HTML-versjon. Levert over fem sesjoner (UX-arbeid +
+renderer-extract + CLI + skill-wiring + release). Ingen scanner-
+eller hook-atferdsendringer — purely additive surface.
+
+### Added
+
+- **Playground katalog list-view + builder-pane** (sesjon 1, `0dc7ff4`).
+  Katalog-overflaten fikk list-view (grid-toggle) + builder-pane med
+  copy-knapp på alle 18 rapporter, så onboarding-flytene blir bredere
+  og dypere uten å forlate playground-modusen.
+- **Playground prosjekt-surface opprydding** (sesjon 2, `86d6ecd`).
+  Stub-screen-håndtering (rapport ikke ferdig parsed → tydelig
+  placeholder i stedet for tom panel), topbar-splitt (navigasjons-
+  trinn vs. eksport-handlinger), generell DS-justering for prosjekt-
+  overflate.
+- **`scripts/lib/report-renderers.mjs`** (sesjon 3, `fa5fb48`).
+  De 18 inline parserne + 18 inline rendererne i playground-HTML-fila
+  flyttet til canonical ESM-modul. Ren overflate: `import { PARSERS,
+  RENDERERS } from './lib/report-renderers.mjs'`. Playground beholder
+  bit-identisk inline-kopi (ESM `import` fungerer ikke fra `file://`
+  uten Chrome/Firefox-flags). Canonical kilde + playground inline = to
+  overflater, samme atferd.
+- **`scripts/render-report.mjs` CLI** (sesjon 4, `db80854`).
+  Zero-dep Node-CLI som tar `commandId` + `--in`/`--out`-flags og
+  konverterer markdown-rapporter til self-contained HTML.
+  Stdin/file/stdout-modus, kebab→camel commandId-routing (alle 18
+  PARSERS fungerer automatisk uten hardkoding). Output inliner 6
+  DS-stylesheets (`tokens`, `base`, `components`, `tier2`, `tier3`,
+  `tier3-supplement`) + lokal `.report-table`-CSS. ~140 KB
+  self-contained HTML; fonter ikke inlined (ville blåst opp 7x til
+  ~1 MB), `tokens.css` har `-apple-system, BlinkMacSystemFont,
+  system-ui` som fallback. Absolutte `file://`-paths i stdout for
+  Ghostty cmd-click. Default output `reports/<command>-<YYYYMMDD-
+  HHmmss>.html` relativt til CWD.
+- **HTML-rapport for alle 18 skill-kommandoer** (sesjon 4-5).
+  Sesjon 4 wired 4 skills (`scan`, `audit`, `posture`, `deep-scan`).
+  Sesjon 5 wired de 14 resterende (`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 en avsluttende "HTML Report"-step
+  som instruerer Claude å (1) compute temp md-path, (2) Write hele
+  markdown-rapporten verbatim, (3) kjøre CLI, (4) appende
+  `> **HTML-rapport:** [Åpne i nettleser](file:///abs/sti.html)`
+  til respons.
+
+### Changed
+
+- Playground beholder inline-kopi av parserne og rendererne for å
+  forbli single-file `file://`-distribuerbar — ESM `import` fungerer
+  ikke fra `file://`-URLs uten Chrome/Firefox-flags. Canonical kilden
+  i `scripts/lib/report-renderers.mjs` og playground inline-kopien er
+  bit-identisk per release.
+
+### Notes
+
+- Pre-existing `pre-compact-scan`-perf-flake (1000 ms terskel under
+  last) gjenstår — defer til v7.7.x patch.
+- Sync-test mellom `scripts/lib/report-renderers.mjs` og playground
+  inline-kopi planlagt som v7.7.x patch (krever scope-utvidelse til
+  `tests/`).
+
 ## [7.6.1] - 2026-05-06
 
 Playground v7.6.0 visuell-patch. Seks bugs fanget under maintainer-
diff --git a/CLAUDE.md b/CLAUDE.md
index 696909a..45393b3 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -1,8 +1,10 @@
-# LLM Security Plugin (v7.6.1)
+# LLM Security Plugin (v7.7.0)
 
-Security scanning, auditing, and threat modeling for Claude Code projects. 5 frameworks: OWASP LLM Top 10, Agentic AI Top 10 (ASI), Skills Top 10 (AST), MCP Top 10, AI Agent Traps (DeepMind). 1822+ unit, integration, and end-to-end tests (`tests/e2e/` covers the multi-hook attack chain, multi-session state simulation, and the full scan-orchestrator pipeline); mutation-testing coverage not published.
+Security scanning, auditing, and threat modeling for Claude Code projects. 5 frameworks: OWASP LLM Top 10, Agentic AI Top 10 (ASI), Skills Top 10 (AST), MCP Top 10, AI Agent Traps (DeepMind). 1820+ unit, integration, and end-to-end tests (`tests/e2e/` covers the multi-hook attack chain, multi-session state simulation, and the full scan-orchestrator pipeline); mutation-testing coverage not published.
 
-Release notes for v7.0.0 → v7.6.1: see `docs/version-history.md` — read on demand.
+Release notes for v7.0.0 → v7.7.0: see `docs/version-history.md` — read on demand.
+
+**v7.7.0 highlights** — All 18 report-producing skill commands now emit a clickable `file://` link to a self-contained HTML version of their markdown report. The new `scripts/render-report.mjs` CLI converts any of the 18 report types via a canonical `scripts/lib/report-renderers.mjs` (18 parsers + 18 renderers, bit-identical to the playground). HTML wraps the Tier 1/2/3 design system inline; no external assets, system fonts only (~140 KB per report). Playground also got list-view, copy-button, and prosjekt-surface cleanup.
 
 ## Commands
 
diff --git a/README.md b/README.md
index ac8597b..bfbe9d8 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@
 
 *AI-generated: all code produced by Claude Code through dialog-driven development. [Full disclosure →](../../README.md#ai-generated-code-disclosure)*
 
-![Version](https://img.shields.io/badge/version-7.6.1-blue)
+![Version](https://img.shields.io/badge/version-7.7.0-blue)
 ![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple)
 ![Commands](https://img.shields.io/badge/commands-20-orange)
 ![Agents](https://img.shields.io/badge/agents-6-orange)
@@ -626,6 +626,7 @@ demonstrations — each with `README.md`, fixture, run script, and
 
 | Version | Date | Highlights |
 |---------|------|------------|
+| **7.7.0** | 2026-05-18 | **HTML-rapport for alle 18 skill-kommandoer.** Hver `/security <cmd>` som produserer rapport printer nå en klikkbar `file://`-lenke til en self-contained HTML-versjon. Levert over 5 sesjoner. (1) Playground katalog list-view + builder-pane med copy-knapp. (2) Playground prosjekt-surface opprydding (stub-screen-håndtering, topbar-splitt). (3) De 18 inline parserne + rendererne i playground-HTML flyttet til canonical ESM-modul `scripts/lib/report-renderers.mjs` (playground beholder bit-identisk inline-kopi siden ESM `import` ikke fungerer fra `file://`). (4) Ny zero-dep CLI `scripts/render-report.mjs` — stdin/file/stdout-modus, kebab→camel commandId-routing, inliner 6 DS-stylesheets + lokal `.report-table`-CSS, ~140 KB self-contained HTML, system-font-fallback, absolutte `file://`-paths for Ghostty cmd-click. (5) Alle 18 skills wired (4 i sesjon 4: scan/audit/posture/deep-scan, 14 i sesjon 5: plugin-audit/mcp-audit/mcp-inspect/ide-scan/supply-check/dashboard/pre-deploy/diff/watch/registry/clean/harden/threat-model/red-team). Output: `reports/<command>-<YYYYMMDD-HHmmss>.html` relativt til CWD. Ingen scanner- eller hook-atferdsendringer — purely additive. |
 | **7.6.1** | 2026-05-06 | **Playground v7.6.0 visuell-patch.** Seks bugs fanget under maintainer-verifisering i nettleser. Alle skyldtes mismatch mellom DS-klasser og rendrer-bruk (eller manglende DS-implementasjoner playground antok eksisterte). (1) `renderFindingsBlock` brukte `.findings` outer som er DS' 2-kolonners list+detail-grid → erstattet med `<section class="report-meta">` + korrekt `findings__list > findings__group`-mønster. (2) `.report-table` manglet helt i DS men brukes i 7+ rendrere → lokal CSS-implementasjon i playground-HTML. (3) `renderPreDeploy` traffic-lights brukte `.sm-card__grade` (28×28 px for én A-F-bokstav) for "PASS"/"PASS-WITH-NOTES"/"FAIL" → erstattet med bredde-tilpasset status-pill. (4) Threat-model matrix-bobler ikke klikkbare → `<button>` med `data-threat-id` + click-handler som scroller til Trusler-tabellen. (5) Radar-labels overlappet ved 6+ akser → SVG 280→380, R 105→125, dynamisk `text-anchor` (start/end/middle) basert på horisontal-posisjon. (6) `recommendation-card__body` overflow på lange tekster → `overflow-wrap: anywhere`. 4/4 fix-spesifikke smoke-tester + 18/18 renderer-regresjon passerer. Ingen scanner- eller hook-atferdsendringer — purely additive surface. |
 | **7.6.0** | 2026-05-06 | **Playground Tier 3-referanse-case.** Playground (`playground/llm-security-playground.html`) hevet til visuelt og strukturelt fullført referanse for `shared/playground-design-system/` Tier 3-supplementet. 8 nye DS-komponenter integrert i de 18 rapport-rendererne: `tfa-flow` + `tfa-leg` + `tfa-arrow` (lethal trifecta-kjede med `<button>`-elementer + ARIA), `mat-ladder` + `mat-step` (5-trinns modenhets-stige med terskler 0/25/50/75/95% PASS), `suppressed-group` (narrative-audit fra `summary.narrative_audit.suppressed_findings`), `codepoint-reveal` + `cp-tag`/`cp-zw`/`cp-bidi` (Unicode-steganografi side-ved-side), `top-risks` + `top-risk[data-severity]` (rangert top-funn-listing, semantisk `<ol>`), `recommendation-card[data-severity]` (severity-tinted advisory på `clean`/`harden`/`audit`/`posture`/`pre-deploy`/`plugin-audit`), `risk-meter` (band-visualisering 0-100 på 5 archetypes), `card--severity-{level}` (severity-color modifier på findings-cards). Wave 1: `badge--scope-security` (identitets-chip), `verdict-pill-lg` (DS Tier 3-pill), `form-progress` + `fp-step` (onboarding-wizard). Slettet ~30 duplikat-CSS-deklarasjoner (DS vinner cascade). 5 nye DS-helpers + `mapSeverityToCardLevel` + `parseNarrativeAudit`. Filendring 10209 → 10677 linjer. Levert over 5 sesjoner, atomic commits. A11Y-rapport oppdatert. Ingen scanner- eller hook-behavior-changes — purely additive surface. |
 | **7.5.0** | 2026-05-05 | **Playground.** Single-file SPA at `playground/llm-security-playground.html` (~10 200 lines) for onboarding, demoer og workshop-bruk uten Claude Code-installasjon. Parsere + renderere for alle 18 `produces_report=true`-kommandoer (Fase 2: 10 høy-prio + Fase 3: 8 gjenstående: mcp-inspect, supply-check, pre-deploy, diff, watch, registry, clean, threat-model). 18 markdown test-fixtures under `playground/test-fixtures/` som kontrakt-anker. Komplett demo-prosjekt `dft-komplett-demo` har alle 18 rapporter ferdig parsed inline. Vendor-synket design-system under `playground/vendor/` (sjekksum-låst). 9 Playwright-genererte screenshots i `playground/screenshots/v7.5.0/`. 11 nye `window`-globaler for testing/automasjon. 2 nye `KEY_STATS_CONFIG`-archetypes (`kanban-buckets`, `matrix-risk`). Bug-fix: `normalizeVerdictText` regex-rekkefølge oppdatert så GO-WITH-CONDITIONS / CONDITIONAL / BETINGET ikke lenger kollapser til ALLOW. Ingen scanner- eller hook-behavior-changes — purely additive surface. |
diff --git a/commands/clean.md b/commands/clean.md
index 85fa2d5..783cd63 100644
--- a/commands/clean.md
+++ b/commands/clean.md
@@ -59,3 +59,23 @@ Validate modified files (JSON parse, frontmatter, `node --check`). Restore from
 
 Output: Pre/post comparison, all fix summaries, remaining manual findings, rollback instructions.
 - Dry-run: show "DRY-RUN" mode, list proposed changes without applying.
+
+## Step 8: HTML Report
+
+After producing the markdown clean report above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-clean-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (pre/post comparison + applied/skipped/failed fix summaries + remaining manual findings + backup/rollback path) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs clean --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/clean-<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 report above is the primary deliverable.
diff --git a/commands/dashboard.md b/commands/dashboard.md
index 19c582f..1e86770 100644
--- a/commands/dashboard.md
+++ b/commands/dashboard.md
@@ -59,3 +59,23 @@ Sort the project table by grade (F first, A last), then by risk score descending
 - If machine grade is C: "Some projects need attention. Run `/security posture` in the worst-graded project."
 - If machine grade is D/F: "Significant exposure. Run `/security audit` in projects graded D/F."
 - If from_cache: "Results cached. Run `/security dashboard --fresh` for a live scan."
+
+## Step 4: HTML Report
+
+After producing the markdown dashboard above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-dashboard-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown dashboard you just produced** (header table with Machine Grade + Project Overview table + Errors + Recommendations) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs dashboard --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/dashboard-<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 dashboard above is the primary deliverable.
diff --git a/commands/diff.md b/commands/diff.md
index fff55d1..5cd3f02 100644
--- a/commands/diff.md
+++ b/commands/diff.md
@@ -96,3 +96,23 @@ Omit Unchanged findings from the output — they add noise. Mention count in sum
 - If resolved > new: "**Improving:** more findings resolved than introduced."
 - If new > 0 and resolved == 0: "**Regression:** X new findings, none resolved."
 - If new == 0 and resolved == 0: "**Stable:** no changes since baseline."
+
+## Step 5: HTML Report
+
+After producing the markdown diff report above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-diff-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (banner with baseline+current timestamps + Summary table + New + Resolved + Moved sections + Advisory) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs diff --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/diff-<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 report above is the primary deliverable.
diff --git a/commands/harden.md b/commands/harden.md
index 0d441c2..110e17e 100644
--- a/commands/harden.md
+++ b/commands/harden.md
@@ -70,3 +70,23 @@ If Grade A not achieved, explain remaining gaps (likely hook-related, which requ
 
 - Grade A: "Configuration hardened. All posture checks pass."
 - Below A: "Configuration improved. Remaining gaps require [hooks/manual setup]. Run `/security posture` for details."
+
+## Step 6: HTML Report
+
+After producing the markdown harden report above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-harden-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (Security Harden header + project metadata + Recommendations + Apply summary + post-apply grade + closing) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs harden --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/harden-<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 report above is the primary deliverable.
diff --git a/commands/ide-scan.md b/commands/ide-scan.md
index 4794892..440a3fb 100644
--- a/commands/ide-scan.md
+++ b/commands/ide-scan.md
@@ -104,3 +104,23 @@ If the user has many sideloaded (`source=vsix`) extensions: suggest re-installin
 - First run with no `--online` is fully offline.
 - Pass a single extracted extension directory to scan just one extension.
 - JetBrains plugins are additionally checked for `Premain-Class` javaagents, `application-components` lifecycle hooks, native binaries (`.so`/`.dylib`/`.dll`/`.jnilib`), long `<depends>` chains, typosquats vs top JetBrains plugins, and shaded-jar advisories (see `knowledge/ide-extension-threat-patterns.md`).
+
+## Step 4: HTML Report
+
+After producing the markdown IDE-scan report above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-ide-scan-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (scanner header table + counts + Per-Extension Results table + Top Findings + Warnings + Recommendations + Notes) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs ide-scan --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/ide-scan-<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 report above is the primary deliverable.
diff --git a/commands/mcp-audit.md b/commands/mcp-audit.md
index db65ab6..2694300 100644
--- a/commands/mcp-audit.md
+++ b/commands/mcp-audit.md
@@ -45,3 +45,23 @@ Parse JSON output. Append a **Live Inspection Results** section:
 - Tool shadowing across servers
 
 **Cross-reference escalation:** If a server was rated "Untrusted" or "Dangerous" in Step 2 AND has live injection findings → escalate to CRITICAL priority in the final report and highlight as "Confirmed active threat (static + live)".
+
+## Step 5: HTML Report
+
+After producing the markdown MCP audit report (Step 3 + optional Step 4 Live Inspection):
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-mcp-audit-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (MCP Landscape Summary + per-server analysis + Live Inspection Results section if `--live` + Keep/Review/Remove groupings + overall risk) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs mcp-audit --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/mcp-audit-<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 report above is the primary deliverable.
diff --git a/commands/mcp-inspect.md b/commands/mcp-inspect.md
index 2a5d6b9..a7baae0 100644
--- a/commands/mcp-inspect.md
+++ b/commands/mcp-inspect.md
@@ -52,3 +52,23 @@ If zero findings: "No injection, shadowing, or drift detected across N servers."
 ## Step 4: Combined Use
 
 Mention: "For combined static + live analysis, use `/security mcp-audit --live`."
+
+## Step 5: HTML Report
+
+After producing the markdown live-inspection report above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-mcp-inspect-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (Live Inspection banner + Server Details table + Findings table + Advisory) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs mcp-inspect --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/mcp-inspect-<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 report above is the primary deliverable.
diff --git a/commands/plugin-audit.md b/commands/plugin-audit.md
index 3ebf597..331a42f 100644
--- a/commands/plugin-audit.md
+++ b/commands/plugin-audit.md
@@ -72,3 +72,23 @@ If `clone_path != null`:
 
 If `evidence_file != null`:
   Run: `node <plugin-root>/scanners/lib/fs-utils.mjs cleanup "<evidence_file>"`
+
+## Step 7: HTML Report
+
+After producing the markdown plugin-audit report (Step 5) and any cleanup (Step 6):
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-plugin-audit-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (plugin metadata + component inventory + permission matrix + hook analysis + security findings + trust verdict) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs plugin-audit --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/plugin-audit-<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 report above is the primary deliverable.
diff --git a/commands/pre-deploy.md b/commands/pre-deploy.md
index db585d4..cdba5d9 100644
--- a/commands/pre-deploy.md
+++ b/commands/pre-deploy.md
@@ -99,3 +99,23 @@ Map the pass count to a risk band and verdict:
 | 0-3/10 | Extreme | Critical risk — deployment blocked until fundamental controls are in place. |
 
 State the verdict and risk band clearly at the end of the report.
+
+## HTML Report
+
+After producing the markdown pre-deploy checklist + verdict above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-pre-deploy-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (10-row checklist table + Manual Verification + Recommendations + Verdict + risk band) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs pre-deploy --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/pre-deploy-<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 checklist above is the primary deliverable.
diff --git a/commands/red-team.md b/commands/red-team.md
index 99d3527..9cf2590 100644
--- a/commands/red-team.md
+++ b/commands/red-team.md
@@ -93,3 +93,23 @@ In adaptive mode, also explain:
 - No network calls, no file modifications, no LLM invocations
 - Safe to run repeatedly — all state is cleaned up after each run
 - Adaptive mode bypasses are **expected** — they document evasion resistance limits
+
+## HTML Report
+
+After producing the markdown red-team narrative report above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-red-team-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (per-category narrative + scenario pass/fail + defense score + adaptive-mode bypasses if `--adaptive`) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs red-team --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/red-team-<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 report above is the primary deliverable.
diff --git a/commands/registry.md b/commands/registry.md
index 8e63470..be2b08b 100644
--- a/commands/registry.md
+++ b/commands/registry.md
@@ -119,3 +119,23 @@ Display results table:
 ```
 
 If no matches: "No entries matching '<pattern>'."
+
+## Step 3: HTML Report
+
+After producing the markdown registry output above (stats / scan-result / search-result, whichever sub-command ran):
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-registry-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown output you just produced** (Skill Signature Registry header + metric table + Recent Entries, OR Registry Hit banner, OR Registry Search results) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs registry --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/registry-<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 output above is the primary deliverable.
diff --git a/commands/supply-check.md b/commands/supply-check.md
index cc13411..930dda7 100644
--- a/commands/supply-check.md
+++ b/commands/supply-check.md
@@ -45,3 +45,23 @@ For each finding, show:
 - Recommendation
 
 Group by severity (CRITICAL first). If zero findings: "No supply chain issues detected in N lockfile(s)."
+
+## Step 5: HTML Report
+
+After producing the markdown supply-check report above:
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-supply-check-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown report you just produced** (banner + lockfile coverage + all findings grouped by severity) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs supply-check --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/supply-check-<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 report above is the primary deliverable.
diff --git a/commands/threat-model.md b/commands/threat-model.md
index 31a7621..ee934ee 100644
--- a/commands/threat-model.md
+++ b/commands/threat-model.md
@@ -25,3 +25,23 @@ Spawn `subagent_type: "llm-security:threat-modeler-agent"`, `model: "opus"`:
 - 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.
diff --git a/commands/watch.md b/commands/watch.md
index 1b8d1de..1430726 100644
--- a/commands/watch.md
+++ b/commands/watch.md
@@ -56,3 +56,23 @@ To run as a system cron job instead:
 
 To stop watching: Escape or Ctrl+C
 ```
+
+## Step 5: HTML Report
+
+After producing the markdown watch banner above (before starting the loop):
+
+1. Compute a temp markdown path:
+   ```bash
+   node -p "require('path').join(require('os').tmpdir(), 'sec-watch-' + Date.now() + '.md')"
+   ```
+2. Use the Write tool to save the **entire markdown banner you just produced** (Security Watch header + baseline timestamp + findings counts + interval + advisory) to that temp path. Verbatim.
+3. Run the renderer:
+   ```bash
+   node <plugin-root>/scripts/render-report.mjs watch --in "<temp-md-path>"
+   ```
+   The CLI writes `reports/watch-<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 banner above is the primary deliverable.
diff --git a/docs/version-history.md b/docs/version-history.md
index a657298..8df9bb8 100644
--- a/docs/version-history.md
+++ b/docs/version-history.md
@@ -45,3 +45,19 @@ Seks bugs fanget av maintainer ved manuell verifisering i nettleser etter v7.6.0
 (6) `recommendation-card__body` tekstoverflyt på lange single-line tekster (vilkår, owner-tags, dato) — lagt `overflow-wrap: anywhere; word-break: break-word` i lokal `<style>`-blokk.
 
 4/4 fix-spesifikke smoke-tester passerer + 18/18 renderere produserer fortsatt komplett HTML mot `dft-komplett-demo` (regresjons-test). Filendring 10677 → 10753 linjer (+76 netto).
+
+## v7.7.0 — HTML-rapport for alle 18 skill-kommandoer
+
+Alle 18 `/security`-kommandoer som produserer rapport får nå en klikkbar `file://`-lenke til en self-contained HTML-versjon. Levert over 5 sesjoner (UX-arbeid + extract + CLI + wiring). Ingen scanner- eller hook-atferdsendringer — purely additive.
+
+**Sesjon 1 (`0dc7ff4`) — Playground katalog list-view + builder-pane.** Katalog-overflaten fikk list-view (grid-toggle) + builder-pane med copy-knapp på alle 18 rapporter, så onboarding-flytene blir bredere/dypere uten å forlate playground-modusen.
+
+**Sesjon 2 (`86d6ecd`) — Playground prosjekt-surface opprydding.** Stub-screen-håndtering (rapport ikke ferdig parsed → tydelig placeholder i stedet for tom panel), topbar-splitt (navigasjons-trinn vs. eksport-handlinger), generell DS-justering for projekt-overflate.
+
+**Sesjon 3 (`fa5fb48`) — `scripts/lib/report-renderers.mjs` extract.** De 18 inline parserne + 18 inline rendererne i playground-HTML-fila flyttet til canonical ESM-modul (`scripts/lib/report-renderers.mjs`) med ren `import { PARSERS, RENDERERS } from './...'`-overflate. Playground beholder en inline-kopi (bit-identisk) fordi ESM `import` ikke fungerer fra `file://` uten Chrome/Firefox-flags. Canonical kilden + playground inline = to overflater, samme atferd.
+
+**Sesjon 4 (`db80854`) — `scripts/render-report.mjs` CLI + 4 skills wired.** Ny zero-dep Node-CLI tar `commandId` + `--in`/`--out` (stdin/file/stdout-modus), bruker kebab→camel-konvertering så alle 18 commandIds fungerer automatisk. Output er self-contained HTML (~140 KB): inlines 6 DS-stylesheets (`tokens`, `base`, `components`, `tier2`, `tier3`, `tier3-supplement`) + lokal `.report-table`-implementasjon. Fonter ikke inlined (ville blåst opp HTML 7x til ~1 MB) — `tokens.css` har `-apple-system, BlinkMacSystemFont, system-ui` som fallback. Absolutte `file://`-paths i stdout for Ghostty cmd-click. Default output `reports/<command>-<YYYYMMDD-HHmmss>.html` relativt til CWD. 4 skills wired: `scan`, `audit`, `posture`, `deep-scan`.
+
+**Sesjon 5 — 14 resterende skills wired + release.** `plugin-audit`, `mcp-audit`, `mcp-inspect`, `ide-scan`, `supply-check`, `dashboard`, `pre-deploy`, `diff`, `watch`, `registry`, `clean`, `harden`, `threat-model`, `red-team` — alle har nå en avsluttende "HTML Report"-step i sin skill-fil som instruerer Claude å (1) compute temp md-path, (2) Write hele markdown-rapporten verbatim, (3) kjøre CLI, (4) appende `> **HTML-rapport:** [Åpne i nettleser](file:///abs/sti.html)` til respons. v7.7.0 release (versjonsbump på tvers av `package.json`, `.claude-plugin/plugin.json`, README badge + state, CLAUDE.md header + state-seksjon, marketplace-rot-README).
+
+Pre-existing `pre-compact-scan`-perf-flake (1000ms terskel under last) gjenstår — defer til v7.7.x patch.
diff --git a/package.json b/package.json
index 143827d..81ce98d 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "llm-security",
-  "version": "7.6.1",
+  "version": "7.7.0",
   "description": "Security scanning, auditing, and threat modeling for Claude Code projects",
   "type": "module",
   "bin": {