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

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

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

3.3 KiB Raw Blame History