Kjell Tore Guttormsen 3b034d9266 feat(llm-security): v7.7.0 — 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 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>

2026-05-18 13:12:21 +02:00

3.4 KiB

Raw Blame History

name	description	allowed-tools	model
security:clean	Scan and remediate security findings — auto-fixes deterministic issues, confirms semi-auto with user, reports manual findings	Read, Glob, Grep, Bash, Write, Edit, Agent, AskUserQuestion	sonnet

/security clean [path] [--dry-run]

Scan, classify findings by remediability, auto-fix deterministic issues, propose semi-auto fixes, report manual. Goal: /security scan yields zero findings after clean.

Step 1: Setup

Parse $ARGUMENTS: extract path (default .), --dry-run flag. Resolve to absolute.
Plugin root = parent of this commands/ folder.
Unless dry-run: create backup via node <plugin-root>/scanners/lib/fs-utils.mjs backup "<target>". Record backup path.

Step 2: Pre-Clean Scan

node <plugin-root>/scanners/lib/fs-utils.mjs tmppath clean-findings.json
node <plugin-root>/scanners/scan-orchestrator.mjs "<target>" --output-file "<findings_file>"

Show banner: Verdict, Risk Score, Finding counts. If 0 findings → stop.

Step 3: Auto-Fix

node <plugin-root>/scanners/auto-cleaner.mjs "<target>" --findings "<findings_file>" [--dry-run]

Report: Applied/Skipped/Failed counts + list of fixes.

Step 4: Semi-Auto Proposals

Collect semi_auto findings from auto-cleaner output. If any, spawn subagent_type: "llm-security:cleaner-agent", model: "sonnet":

Here are semi-auto findings: <JSON>. Target: <target>. Read: <plugin-root>/knowledge/secrets-patterns.md Return remediation proposals as JSON.

Present each proposal group via AskUserQuestion: "Apply all" / "Review individually" / "Skip". Apply approved fixes with Edit tool. Skip if dry-run.

Step 5: LLM Threat Scan

Spawn subagent_type: "llm-security:skill-scanner-agent", model: "sonnet":

Scan target: <target>. Read: <plugin-root>/knowledge/skill-threat-patterns.md, <plugin-root>/knowledge/secrets-patterns.md Return findings with severity, category, file, line, remediation.

Auto-fix deterministic LLM findings (injection comments, spoofed headers, exfil URLs). Present semi-auto via AskUserQuestion. Report manual findings.

Step 6: Validate + Re-Scan

Validate modified files (JSON parse, frontmatter, node --check). Restore from backup on failure. Re-run orchestrator to measure improvement.

Step 7: Report

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:

Compute a temp markdown path:

node -p "require('path').join(require('os').tmpdir(), 'sec-clean-' + Date.now() + '.md')"

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.
Run the renderer:
```
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.
Append to your response (markdown link, no bare URL):

HTML-rapport: Åpne i nettleser

If the CLI exits non-zero, mention the error but do not block — the markdown report above is the primary deliverable.

3.4 KiB Raw Blame History