Kjell Tore Guttormsen
3b034d9266
Hver /security <cmd> som produserer rapport printer nå en klikkbar file://-lenke til en self-contained HTML-versjon. Levert over fem sesjoner; sesjon 5 wirer de 14 resterende skill-filene + slipper v7.7.0 (versjonsbump + docs). Sesjon-historikk: - Sesjon 1 (0dc7ff4) — playground katalog list-view + builder-pane med copy-knapp på alle 18 rapporter - Sesjon 2 (86d6ecd) — playground prosjekt-surface opprydding (stub-screen + topbar-splitt) - Sesjon 3 (fa5fb48) — extract 18 inline parsers + 18 inline renderers fra playground til canonical ESM-modul scripts/lib/report-renderers.mjs (playground beholder bit-identisk inline-kopi siden ESM import ikke fungerer fra file://) - Sesjon 4 (db80854) — ny zero-dep CLI scripts/render-report.mjs (stdin/file/stdout-modus, kebab→camel commandId-routing, ~140 KB self-contained HTML med 6 inlined DS-stylesheets + lokal .report-table, absolutte file://-paths for Ghostty cmd-click). 4 skills wired: scan, audit, posture, deep-scan. - Sesjon 5 (denne) — 14 resterende skills wired: plugin-audit, mcp-audit, mcp-inspect, ide-scan, supply-check, dashboard, pre-deploy, diff, watch, registry, clean, harden, threat-model, red-team. Hver skill-fil har nå en HTML Report-step som instruerer Claude å skrive markdown verbatim, kjøre CLI, og appende klikkbar file://-lenke til respons. Release-arbeid: - Versjonsbump v7.6.1 → v7.7.0 i 6 plugin-filer + 2 rot-filer (package.json, .claude-plugin/plugin.json, README badge, CLAUDE.md header + state-seksjon, docs/version-history.md, plugin Recent versions- tabell, rot README plugin-entry, rot CLAUDE.md plugin-katalog) - CHANGELOG [7.7.0] med full historikk fra sesjon 1-5 - docs/version-history.md v7.7.0-seksjon Verifisert: - 18/18 commandIds i CLI gir > 138 KB self-contained HTML - 1819/1820 tester grønne (pre-compact-scan-perf-flake fyrte under last, passerer i isolasjon på 1582 ms — pre-eksisterende, defer til v7.7.x) - 18/18 skill-filer har HTML Report-step - Ingen kildefil-treff på 7.6.1 utenfor historiske changelog/version- history/README releases-tabell Ingen scanner- eller hook-atferdsendringer — purely additive surface. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
92 lines
3.1 KiB
Markdown
92 lines
3.1 KiB
Markdown
---
|
|
name: security:harden
|
|
description: Generate Grade A security configuration — settings.json, CLAUDE.md security section, .gitignore additions
|
|
allowed-tools: Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion
|
|
model: 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:
|
|
|
|
1. Compute a temp markdown path:
|
|
```bash
|
|
node -p "require('path').join(require('os').tmpdir(), 'sec-harden-' + Date.now() + '.md')"
|
|
```
|
|
2. 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.
|
|
3. Run the renderer:
|
|
```bash
|
|
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.
|
|
4. Append to your response (markdown link, no bare URL):
|
|
|
|
> **HTML-rapport:** [Åpne i nettleser](file:///abs/path.html)
|
|
|
|
If the CLI exits non-zero, mention the error but do not block — the markdown report above is the primary deliverable.
|