openclaw-triage – OpenClaw Skill

---

name: openclaw-triage description: "Incident response and forensics for agent workspaces. Investigate compromises, build timelines, assess blast radius, and collect evidence. Cross-references data from warden, ledger, signet, and sentinel for unified analysis. Free alert layer — upgrade to openclaw-triage-pro for automated containment, remediation playbooks, and evidence export." user-invocable: true metadata: {"openclaw":{"emoji":"🚨","requires":{"bins":["python3"]},"os":["darwin","linux","win32"]}}

OpenClaw Triage

Incident response and forensics for agent workspaces. When something goes wrong — a skill behaves unexpectedly, files change without explanation, or another security tool flags an anomaly — triage investigates what happened, assesses the damage, and guides recovery.

This is the "detective" that pulls together evidence from all OpenClaw security tools into a unified incident report.

Need automated containment and remediation? Upgrade to openclaw-triage-pro for quarantine, playbooks, evidence chain-of-custody, and post-incident hardening.

Commands

Full Investigation

Run a comprehensive incident investigation. Collects workspace state, checks for signs of compromise (recently modified critical files, new skills, unusual permissions, off-hours modifications, large files, hidden files), cross-references with warden/ledger/signet/sentinel data, builds an event timeline, and calculates an incident severity score (CRITICAL / HIGH / MEDIUM / LOW).

python3 {baseDir}/scripts/triage.py investigate --workspace /path/to/workspace

Event Timeline

Build a chronological timeline of all file modifications in the workspace. Groups events by hour, highlights suspicious burst activity (many files modified in a short window), shows which directories and skills were affected, and cross-references with ledger entries if available.

python3 {baseDir}/scripts/triage.py timeline --workspace /path/to/workspace

Look back further than the default 24 hours:

python3 {baseDir}/scripts/triage.py timeline --hours 72 --workspace /path/to/workspace

Blast Radius (Scope)

Assess the blast radius of a potential compromise. Categorizes all files by risk level (critical, memory, skill, config), checks for credential exposure patterns in recently modified files, scans for outbound exfiltration URLs, and estimates scope as CONTAINED (single area), SPREADING (multiple skills), or SYSTEMIC (workspace-level).

python3 {baseDir}/scripts/triage.py scope --workspace /path/to/workspace

Evidence Collection

Collect and preserve forensic evidence before remediation. Snapshots the full workspace state (file list with SHA-256 hashes, sizes, timestamps), copies all available security tool data (.integrity/, .ledger/, .signet/, .sentinel/), and generates a summary report. Always run this before any remediation to preserve the forensic trail.

python3 {baseDir}/scripts/triage.py evidence --workspace /path/to/workspace

Save to a custom output directory:

python3 {baseDir}/scripts/triage.py evidence --output /path/to/evidence/dir --workspace /path/to/workspace

Quick Status

One-line summary of triage state: last investigation timestamp, current threat level, and whether evidence has been collected.

python3 {baseDir}/scripts/triage.py status --workspace /path/to/workspace

Workspace Auto-Detection

If --workspace is omitted, the script tries:

1. OPENCLAW_WORKSPACE environment variable
2. Current directory (if AGENTS.md exists)
3. ~/.openclaw/workspace (default)

Cross-Reference Sources

Triage automatically checks for data from these OpenClaw tools:

Tool	Data Path	What Triage Checks
Warden	.integrity/manifest.json	Baseline deviations — files modified since last known-good state
Ledger	.ledger/chain.jsonl	Chain breaks, unparseable entries, suspicious log entries
Signet	.signet/manifest.json	Tampered skill signatures — skills modified after signing
Sentinel	.sentinel/threats.json	Known threats and high-severity findings

Incident Severity Levels

Level	Meaning	Trigger
CRITICAL	Immediate response required	Any critical finding, or 3+ high findings
HIGH	Investigation warranted	High-severity findings from any source
MEDIUM	Review recommended	Multiple medium findings or volume threshold
LOW	No immediate action	Informational findings only

Exit Codes

• 0 — Clean, no actionable findings
• 1 — Findings detected (investigation recommended)
• 2 — Critical findings (immediate action needed)

No External Dependencies

Python standard library only. No pip install. No network calls. Everything runs locally.

Cross-Platform

Works with OpenClaw, Claude Code, Cursor, and any tool using the Agent Skills specification.

OpenClaw Triage

Free incident response and forensics for OpenClaw, Claude Code, and any Agent Skills-compatible tool.

Investigates compromises, builds event timelines, assesses blast radius, and collects forensic evidence — pulling together data from warden, ledger, signet, and sentinel into unified incident reports.

Looking for automated containment and remediation? See openclaw-triage-pro for quarantine, playbooks, evidence chain-of-custody, and post-incident hardening.

The Problem

When something goes wrong in an agent workspace — unexpected file changes, anomalous skill behavior, or a security tool flags an alert — you need to quickly understand what happened, how far it spread, and what to do about it.

Existing OpenClaw security tools each monitor one dimension: warden watches file integrity, ledger tracks the audit chain, signet verifies skill signatures, sentinel scans for threats. But no single tool correlates all of that data into a coherent incident picture.

Triage is the detective that ties it all together.

Install

# Clone
git clone https://github.com/AtlasPA/openclaw-triage.git

# Copy to your workspace skills directory
cp -r openclaw-triage ~/.openclaw/workspace/skills/

Usage

# Full incident investigation
python3 scripts/triage.py investigate

# Build event timeline (last 24 hours)
python3 scripts/triage.py timeline

# Timeline with custom window
python3 scripts/triage.py timeline --hours 72

# Assess blast radius
python3 scripts/triage.py scope

# Collect forensic evidence
python3 scripts/triage.py evidence

# Evidence to custom directory
python3 scripts/triage.py evidence --output /path/to/dir

# Quick status check
python3 scripts/triage.py status

All commands accept --workspace /path/to/workspace. If omitted, auto-detects from $OPENCLAW_WORKSPACE, current directory, or ~/.openclaw/workspace.

What It Does

Investigate

Runs a comprehensive incident investigation:

• Workspace inventory — Collects file hashes, modification times, and sizes for every file
• Compromise indicators — Checks for recently modified critical files (SOUL.md, AGENTS.md, etc.), new/modified skills, off-hours modifications, large files, and hidden files
• Cross-reference — Pulls data from warden (baseline deviations), ledger (chain breaks), signet (tampered signatures), and sentinel (known threats)
• Timeline — Builds a summary of recent events based on file modification times
• Severity scoring — Calculates an overall incident severity: CRITICAL, HIGH, MEDIUM, or LOW

Timeline

Builds a detailed chronological view of workspace activity:

• Lists all file modifications grouped by hour
• Highlights suspicious burst activity (many files modified in a short window)
• Shows which directories and skills were affected
• Cross-references with ledger entries if available

Scope

Assesses the blast radius of a potential compromise:

• Categorizes all files by risk: critical workspace files, memory files, skill files, config files
• Scans recently modified files for credential exposure patterns (API keys, tokens, AWS keys)
• Scans for outbound exfiltration URLs (ngrok, webhook.site, raw IPs, etc.)
• Estimates scope level: CONTAINED, SPREADING, or SYSTEMIC

Evidence Collection

Preserves forensic data before remediation:

• Snapshots full workspace state (file list with SHA-256 hashes, sizes, timestamps)
• Copies all security tool data (.integrity/, .ledger/, .signet/, .sentinel/)
• Generates a collection summary
• Saves everything to .triage/evidence-{timestamp}/ or a custom directory

Always run evidence collection before any remediation to preserve the forensic trail.

Status

Quick check of triage state: last investigation timestamp, current threat level, and whether evidence has been collected.

Cross-Reference Sources

Tool	Data Path	What Triage Checks
Warden	.integrity/manifest.json	Baseline deviations
Ledger	.ledger/chain.jsonl	Chain breaks, suspicious entries
Signet	.signet/manifest.json	Tampered skill signatures
Sentinel	.sentinel/threats.json	Known threats

Exit Codes

Code	Meaning
0	Clean, no actionable findings
1	Findings detected (investigation recommended)
2	Critical findings (immediate action needed)

Free vs Pro

Feature	Free	Pro
Full investigation	Yes	Yes
Event timeline	Yes	Yes
Blast radius assessment	Yes	Yes
Evidence collection	Yes	Yes
Cross-reference (warden, ledger, signet, sentinel)	Yes	Yes
Severity scoring	Yes	Yes
Automated containment (quarantine affected skills)	-	Yes
Critical file restore from backup	-	Yes
Remediation playbooks	-	Yes
Evidence chain-of-custody	-	Yes
Incident report export (JSON, HTML)	-	Yes
Integration hooks with all OpenClaw tools	-	Yes
Post-incident hardening recommendations	-	Yes

Requirements

• Python 3.8+
• No external dependencies (stdlib only)
• Cross-platform: Windows, macOS, Linux

License

MIT