open/llm-security
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions
llm-security/commands/dashboard.md
Kjell Tore Guttormsen f153f969a0 feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command 
Add /ultraresearch-local for structured research combining local codebase
analysis with external knowledge via parallel agent swarms. Produces research
briefs with triangulation, confidence ratings, and source quality assessment.

New command: /ultraresearch-local with modes --quick, --local, --external, --fg.
New agents: research-orchestrator (opus), docs-researcher, community-researcher,
security-researcher, contrarian-researcher, gemini-bridge (all sonnet).
New template: research-brief-template.md.

Integration: --research flag in /ultraplan-local accepts pre-built research
briefs (up to 3), enriches the interview and exploration phases. Planning
orchestrator cross-references brief findings during synthesis.

Design principle: Context Engineering — right information to right agent at
right time. Research briefs are structured artifacts in the pipeline:
ultraresearch → brief → ultraplan --research → plan → ultraexecute.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-08 08:58:35 +02:00

1.9 KiB
Raw Blame History

name description allowed-tools model
security:dashboard Cross-project security dashboard — machine-wide posture overview with per-project grades Read, Glob, Grep, Bash 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."