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>
78 lines
2.5 KiB
Markdown
78 lines
2.5 KiB
Markdown
---
|
|
name: security:watch
|
|
description: Continuous security monitoring — runs diff on a recurring interval
|
|
allowed-tools: Bash, Read, Skill
|
|
model: sonnet
|
|
---
|
|
|
|
# /security watch [path] [--interval 6h]
|
|
|
|
Set up continuous security monitoring. Establishes a baseline, then runs `/security diff` on a recurring interval to detect regressions.
|
|
|
|
## Step 1: Parse Arguments
|
|
|
|
Extract from `$ARGUMENTS`:
|
|
- **path** — first non-flag argument (default `.`)
|
|
- **--interval \<value\>** — loop interval like `6h`, `30m`, `1h` (default `6h`)
|
|
|
|
## Step 2: Establish Baseline
|
|
|
|
Determine plugin root (parent of this `commands/` folder) and resolve the target path.
|
|
|
|
```bash
|
|
node <plugin-root>/scanners/scan-orchestrator.mjs "<target>" --save-baseline
|
|
```
|
|
|
|
Parse stdout JSON. Display:
|
|
|
|
```
|
|
## Security Watch: <target>
|
|
|
|
**Baseline established** at <timestamp>
|
|
**Findings:** XC XH XM XL XI | **Risk Score:** X/100 | **Verdict:** ALLOW/WARNING/BLOCK
|
|
|
|
Starting watch with interval: <interval>
|
|
```
|
|
|
|
If the verdict is BLOCK, add a warning: "Initial scan shows BLOCK verdict — you will be alerted to any new findings above this baseline."
|
|
|
|
## Step 3: Start Loop
|
|
|
|
Use the **Skill** tool to invoke the built-in `/loop` skill:
|
|
- skill: `loop`
|
|
- args: `<interval> /security diff <target>`
|
|
|
|
This runs `/security diff <target>` every `<interval>`. Each diff compares against the latest baseline and saves a new one — a rolling window of changes.
|
|
|
|
## Step 4: Advisory
|
|
|
|
After starting the loop, display:
|
|
|
|
```
|
|
**Watch active.** `/security diff <target>` runs every <interval>.
|
|
|
|
To run as a system cron job instead:
|
|
node <plugin-root>/scanners/watch-cron.mjs
|
|
|
|
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.
|