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

Raw Blame History

name	description	allowed-tools	model
security:posture	Quick security posture assessment — scorecard with grade, coverage status, and top recommendations	Read, Glob, Grep, Bash	sonnet

/security posture

Quick security scorecard — grade, coverage, top recommendations. Deterministic scanner, <2 sec.

Step 1: Run Scanner

Run the deterministic posture scanner:

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

Parse the JSON output. The result contains:

scoring.grade (A-F), scoring.pass_rate, scoring.pass/partial/fail/na
risk.score (0-100), risk.band, risk.verdict
categories[] with id, name, status, findings_count, evidence
findings[] with severity, title, description, owasp, recommendation
counts with critical/high/medium/low/info

Step 2: Format Scorecard

Present the results as a scorecard:

# Security Posture — [project name]

| Field | Value |
|-------|-------|
| **Grade** | [A-F] |
| **Risk Score** | [N]/100 ([band]) |
| **Verdict** | [verdict] |
| **Duration** | [N]ms |

## Category Scorecard

| # | Category | Status | Findings |
|---|----------|--------|----------|
[one row per category, status as PASS/PARTIAL/FAIL/N-A]

## Top Findings

[List critical and high findings with title, file, and recommendation]

## Quick Wins

[List low-effort fixes from findings]

Step 3: Closing

Grade A/B: "Posture solid. Re-run after major changes."
Grade C: "Run /security audit for detailed findings."
Grade D/F: "Significant exposure. Run /security audit before production use."

Step 4: HTML Report

After producing the markdown scorecard above:

Compute a temp markdown path:

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

Use the Write tool to save the entire markdown scorecard you just produced (header + Category Scorecard table + Top Findings + Quick Wins + closing) to that temp path. Verbatim.
Run the renderer:
```
node <plugin-root>/scripts/render-report.mjs posture --in "<temp-md-path>"
```
The CLI writes reports/posture-<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 scorecard above is the primary deliverable.

2.4 KiB Raw Blame History