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>
81 lines
2.8 KiB
Markdown
81 lines
2.8 KiB
Markdown
---
|
|
name: security:dashboard
|
|
description: Cross-project security dashboard — machine-wide posture overview with per-project grades
|
|
allowed-tools: Read, Glob, Grep, Bash
|
|
model: sonnet
|
|
---
|
|
|
|
# /security dashboard
|
|
|
|
Machine-wide security dashboard. Discovers all Claude Code projects, runs posture-scanner on each, shows aggregated overview.
|
|
|
|
## Step 1: Run Dashboard Aggregator
|
|
|
|
Run the aggregator (uses 24h cache by default):
|
|
|
|
```
|
|
node <this plugin's scanners/dashboard-aggregator.mjs>
|
|
```
|
|
|
|
If user specified `--no-cache` or `--fresh`, add `--no-cache` flag.
|
|
|
|
Parse the JSON output. The result contains:
|
|
- `meta.scanner`, `meta.version`, `meta.timestamp`, `meta.from_cache`
|
|
- `machine.grade` (weakest link), `machine.projects_scanned`, `machine.total_findings`, `machine.counts`
|
|
- `projects[]` with path, display_name, grade, risk_score, risk_band, worst_category, worst_status, findings_count, counts
|
|
- `errors[]` with path, display_name, error
|
|
|
|
## Step 2: Format Dashboard
|
|
|
|
Present the results:
|
|
|
|
```
|
|
# Security Dashboard
|
|
|
|
| Field | Value |
|
|
|-------|-------|
|
|
| **Machine Grade** | [A-F] (weakest link) |
|
|
| **Projects Scanned** | [N] |
|
|
| **Total Findings** | [N] |
|
|
| **Scan Time** | [N]ms |
|
|
| **Cache** | [Fresh scan / Cached (age)] |
|
|
|
|
## Project Overview
|
|
|
|
| Project | Grade | Risk | Worst Category | Findings |
|
|
|---------|-------|------|----------------|----------|
|
|
[one row per project, sorted by grade (worst first)]
|
|
|
|
## Errors
|
|
|
|
[List any projects that failed to scan, if any]
|
|
```
|
|
|
|
Sort the project table by grade (F first, A last), then by risk score descending.
|
|
|
|
## Step 3: Recommendations
|
|
|
|
- If machine grade is A/B: "Machine posture is solid. Re-run after major changes or new plugin installs."
|
|
- If machine grade is C: "Some projects need attention. Run `/security posture` in the worst-graded project."
|
|
- If machine grade is D/F: "Significant exposure. Run `/security audit` in projects graded D/F."
|
|
- If from_cache: "Results cached. Run `/security dashboard --fresh` for a live scan."
|
|
|
|
## Step 4: HTML Report
|
|
|
|
After producing the markdown dashboard above:
|
|
|
|
1. Compute a temp markdown path:
|
|
```bash
|
|
node -p "require('path').join(require('os').tmpdir(), 'sec-dashboard-' + Date.now() + '.md')"
|
|
```
|
|
2. Use the Write tool to save the **entire markdown dashboard you just produced** (header table with Machine Grade + Project Overview table + Errors + Recommendations) to that temp path. Verbatim.
|
|
3. Run the renderer:
|
|
```bash
|
|
node <plugin-root>/scripts/render-report.mjs dashboard --in "<temp-md-path>"
|
|
```
|
|
The CLI writes `reports/dashboard-<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 dashboard above is the primary deliverable.
|