ktg-plugin-marketplace/plugins/llm-security/commands/watch.md
Kjell Tore Guttormsen 03b8885b6e chore(llm-security): v7.7.2 — language consistency pass
~/.claude/CLAUDE.md specifies English for code and documentation,
Norwegian for dialog only. Norwegian had crept into surface text
across v7.5-v7.7. Translated to English in eight surfaces.

No scanner, hook, or behavior changes — purely surface text.

- 18 skill commands: the HTML Report-step now reads "HTML report:
  [Open in browser]" instead of "HTML-rapport: [Åpne i nettleser]"
- scripts/lib/report-renderers.mjs: key-stat labels, lede defaults,
  table headers, maturity-ladder descriptions, action-tier labels,
  clean buckets, dry-run/apply copy, and JS comments. Regex
  alternations /^high|^høy/ and /resolution|løsning/i preserved.
- playground/llm-security-playground.html: same renderer changes
  mirrored bit-identical, plus playground-only UI strings (catalog,
  breadcrumb aria-label, theme toggle, builder-modal hint,
  guide-panel "no projects yet", delete confirmation, alert/copy).
  Demo-state fixture content for dft-komplett-demo preserved
  (intentional Norwegian persona).
- agents/skill-scanner-agent.md + agents/mcp-scanner-agent.md:
  Generaliseringsgrense + Parallell Read-strategi sections translated
  to Generalization boundary + Parallel Read strategy.
- README.md: playground architecture prose + Recent versions table
  (v7.5.0 — v7.7.1).
- CLAUDE.md: v7.7.1 highlights translated, new v7.7.2 highlights
  added.
- ../../README.md: llm-security v7.5.0 — v7.7.1 bullets.
- ../../CLAUDE.md: llm-security catalog entry.
- docs/scanner-reference.md: six runnable-examples table cells.
- docs/version-history.md: new v7.7.2 entry. v7.5-v7.7 narrative
  sections left in original language (deferred per operator).
- Version bumped 7.7.1 → 7.7.2 in package.json,
  .claude-plugin/plugin.json, README badge + Recent versions,
  CLAUDE.md header + state, docs/version-history.md, playground
  renderHome hardcoded string, root README + CLAUDE.md llm-security
  entries.

Tests: 1820/1820 green. CLI smoke-test: 18/18 commandIds produce
>138 KB self-contained HTML. Browser-dogfood verified.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-19 06:47:44 +02:00

2.5 KiB

name description allowed-tools model
security:watch Continuous security monitoring — runs diff on a recurring interval Bash, Read, Skill 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.

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:

    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:

    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 report: Open in browser

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