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

Raw Blame History

name	description	allowed-tools	model
security:audit	Full project security audit with OWASP LLM Top 10 assessment, scoring, and remediation plan	Read, Glob, Grep, Bash, Agent	sonnet

/security audit

Full security audit — 10 categories, OWASP LLM Top 10 aligned, A-F grade.

Step 1: Run Posture Scanner

Run the deterministic posture scanner first for instant category results:

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

Parse JSON output. Record: grade, risk score, all category statuses, all findings.

Step 2: Gather Context

Read CLAUDE.md for project name and type
Glob for: commands/*.md, agents/*.md, .mcp.json, **/.mcp.json, .claude-plugin/plugin.json
Determine: has skills/commands? has MCP servers?

Step 3: Skill Scan (if commands/agents found)

Spawn subagent_type: "llm-security:skill-scanner-agent", model: "sonnet":

Scan all commands/ and agents/ at [cwd]. Read: <plugin-root>/knowledge/skill-threat-patterns.md Return findings: file, issue, severity, OWASP ref.

Step 4: MCP Scan (if MCP servers found)

After skill scan, spawn subagent_type: "llm-security:mcp-scanner-agent", model: "sonnet":

Audit MCP configs at [cwd]. Read: <plugin-root>/knowledge/mcp-threat-patterns.md Return trust table and findings with severity.

Step 5: Generate Report

Merge posture scanner JSON + agent findings. Use the posture scanner's grade as the baseline. Recalculate risk_score = riskScore(counts) (severity-dominated v2 model — see scanners/lib/severity.mjs) including agent findings.

Output: Risk Dashboard, Executive Summary, 10 Category Sections (use scanner evidence + agent narrative), Summary Table, Action Items (IMMEDIATE → HIGH → MEDIUM).

Close with top 2-3 action items. If grade C or lower: suggest /security threat-model.

Step 6: HTML Report

After producing the markdown audit report above:

Compute a temp markdown path:

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

Use the Write tool to save the entire markdown report you just produced (Risk Dashboard + Executive Summary + Category Sections + Summary Table + Action Items) to that temp path. Verbatim.
Run the renderer:
```
node <plugin-root>/scripts/render-report.mjs audit --in "<temp-md-path>"
```
The CLI writes reports/audit-<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 audit above is the primary deliverable.

2.7 KiB Raw Blame History