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.1 KiB

Raw Blame History

name	description	allowed-tools	model
security:harden	Generate Grade A security configuration — settings.json, CLAUDE.md security section, .gitignore additions	Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion	sonnet

/security harden [path] [--apply] [--dry-run]

Generate reference security configuration to achieve Grade A posture. Runs posture scanner, identifies gaps, generates config to close them.

Step 1: Generate

Run the reference configuration generator:

node <this plugin's scanners/reference-config-generator.mjs> [target-path or cwd] [--apply]

Default is --dry-run (show JSON output, do not write files).

Parse the JSON output. The result contains:

projectType: plugin, monorepo, or standalone
posture: current grade, pass_rate, pass/partial/fail counts
recommendations[]: file, action (create/merge/append/none), content, category
summary: total, actionable, creates, merges, appends

Step 2: Present Results

# Security Harden — [project name]

| Field | Value |
|-------|-------|
| **Current Grade** | [grade] |
| **Project Type** | [type] |
| **Recommendations** | [actionable]/[total] |

## Recommendations

[For each recommendation with action != 'none':]
### [N]. [category] — [file]
- **Action:** [create/merge/append]
- **Content preview:** [first 3 lines or summary]

Step 3: Apply (if --apply or user confirms)

If $ARGUMENTS contains --apply, the generator already wrote files. Report what was changed.

If $ARGUMENTS is --dry-run or empty, ask the user:

"Apply these [N] changes? This will create a backup first."

If confirmed, re-run with --apply. Report backup location and files written.

Step 4: Post-Apply Verification

After applying, re-run posture scanner to verify improvement:

node <this plugin's scanners/posture-scanner.mjs> [target-path]

Report: "Grade improved from [old] to [new]." or "Grade unchanged at [grade]."

If Grade A not achieved, explain remaining gaps (likely hook-related, which require manual setup or plugin installation).

Step 5: Closing

Grade A: "Configuration hardened. All posture checks pass."
Below A: "Configuration improved. Remaining gaps require [hooks/manual setup]. Run /security posture for details."

Step 6: HTML Report

After producing the markdown harden report above:

Compute a temp markdown path:

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

Use the Write tool to save the entire markdown report you just produced (Security Harden header + project metadata + Recommendations + Apply summary + post-apply grade + closing) to that temp path. Verbatim.
Run the renderer:
```
node <plugin-root>/scripts/render-report.mjs harden --in "<temp-md-path>"
```
The CLI writes reports/harden-<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.1 KiB Raw Blame History