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

4.6 KiB

Raw Blame History

name	description	allowed-tools	model
security:plugin-audit	Audit a Claude Code plugin for security risks, permission analysis, and trust assessment before installation	Read, Glob, Grep, Bash, Agent	sonnet

/security plugin-audit [path|url]

Audit a Claude Code plugin for security before installation. Accepts local paths or GitHub URLs.

Step 1: Resolve Target

If $ARGUMENTS contains --branch <name> → strip it, set branch = <name>
If $ARGUMENTS starts with https://github.com/ or git@github.com: → Run: node <plugin-root>/scanners/lib/git-clone.mjs clone "<url>" [--branch <branch>] If exit code != 0 → show error to user and STOP Set clone_path = stdout (trimmed), target = clone_path Set remote_url = <url> for display
Else if $ARGUMENTS is non-empty → target = $ARGUMENTS, clone_path = null
Else → target = ".", clone_path = null
Verify .claude-plugin/plugin.json exists at <target>. If not and clone_path != null → cleanup clone_path first, then tell user this is not a plugin directory and STOP. If not and local → tell user and STOP.

IMPORTANT: Cleanup Guarantee (remote audits)

If clone_path != null, the following cleanup MUST run regardless of audit outcome. If ANY step between clone and cleanup fails or errors, STILL run cleanup before stopping:

node <plugin-root>/scanners/lib/git-clone.mjs cleanup "<clone_path>"
node <plugin-root>/scanners/lib/fs-utils.mjs cleanup "<evidence_file>" (if evidence_file is set)

Step 1.5: Pre-extraction (remote audits only)

If clone_path != null: Get temp path: node <plugin-root>/scanners/lib/fs-utils.mjs tmppath "plugin-extract.json" Run: node <plugin-root>/scanners/content-extractor.mjs "<target>" --output-file "<evidence_file>" If exit code != 0 → set evidence_file = null (fall back to direct scan)

Step 2: Inventory

Read plugin.json (name, version, auto_discover). Glob for commands, agents, hooks, skills, knowledge. Build permission matrix from all allowed-tools and tools declarations. Flag: Bash access, Bash+Write combo, Task (sub-agent spawning), opus for trivial tasks.

Step 3: Analyze Hooks

If hooks/hooks.json exists: parse events, read scripts, classify (block/warn/modify). Flag: state modification, network calls, non-CLAUDE env vars, SessionStart hooks.

Step 4: Scan Content

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

If evidence_file is set:

EVIDENCE-PACKAGE MODE. Read: <evidence_file> Read: <plugin-root>/knowledge/skill-threat-patterns.md Analyze all sections. DO NOT use Read/Glob/Grep on the target directory. Check all 7 threat categories. Return findings: file, severity, OWASP ref.

Otherwise:

Scan plugin at <path>: commands/.md, agents/.md, hooks/scripts/, skills//SKILL.md, knowledge/**/*.md. Read: <plugin-root>/knowledge/skill-threat-patterns.md Check all 7 threat categories. Return findings: file, severity, OWASP ref.

Step 5: Report

Output: Plugin metadata, component inventory, permission matrix, hook analysis, security findings, trust verdict.

Verdict: Install (0 critical/high, transparent hooks) | Review (high findings or unclear permissions) | Do Not Install (critical, exfiltration, persistence, or hidden instructions).

Step 6: Cleanup (only if remote)

If clone_path != null: Run: node <plugin-root>/scanners/lib/git-clone.mjs cleanup "<clone_path>" If cleanup fails → warn: "Could not remove temp dir <clone_path> — remove manually."

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):

Compute a temp markdown path:

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

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.
Run the renderer:
```
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.
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.

4.6 KiB Raw Blame History