rca

rca is a skill for Claude Code from bjornjee/agent-dashboard. It costs 30 tokens per session (2,484 once invoked), scanned C, original, MIT.

A troubleshooting workflow for finding the cause of crashed processes, stopped servers, and other system failures on macOS. It uses logs, session history, and code tracing before drawing conclusions.

In plain words
What is it for?
Use it to examine crash windows, running sessions, shell history, agent logs, and related code while investigating an unexplained failure.
Why use it?
It helps replace guesswork with an evidence-based investigation when it is unclear why a program or service stopped.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Part of the agent-dashboard plugin — 8 skills, 5 agents, 10 hooks shipped together

Good fit Use it to examine crash windows, running sessions, shell history, agent logs, and related code while investigating an unexplained failure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bjornjee/agent-dashboard/rca
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add bjornjee/agent-dashboard --skill rca
Clone the repo
git clone --depth 1 https://github.com/bjornjee/agent-dashboard

Made for: Claude Code.

Or install agent-dashboard, the plugin that ships this one along with the rest of its 8 skills, 5 agents, 10 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for rca

README.md
[![agentmods](https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/rca/github.svg)](https://agentmods.dev/skills/bjornjee/agent-dashboard/rca)
Your own site
<a href="https://agentmods.dev/skills/bjornjee/agent-dashboard/rca"><img src="https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/rca/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for rca

Your own site · 80×15
<a href="https://agentmods.dev/skills/bjornjee/agent-dashboard/rca"><img src="https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/rca.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,484 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.02484
Opus 5.5 $0.00012 $0.00994
Sonnet 5.5 $0.00006 $0.00497
Haiku 4.5 $0.00003 $0.00248

Measured 1mo ago against content hash 2d7ce2451e3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

rca scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- `rm -rf`, `git clean`, `git reset --hard` (destructive ops)
adapters/claude-code/skills/rca/SKILL.md · 249 lines

How it starts

The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Root cause analysis for a system-level failure. Gather ALL evidence before reasoning about the cause.

Incident description: $ARGUMENTS

Instructions

Follow these phases strictly in order. Every phase has a gate. Do not speculate about cause until Phase 5.


Phase 1: Scope the Incident

  1. Parse the incident description — what died? (process, tmux server, container, service, etc.)

  2. Establish the time window: ask the user or derive from context when the failure was noticed and when things last worked.

  3. Identify what was running at the time — check:

    • tmux list-sessions / tmux list-panes -a (if tmux is back up)
    • Shell history with timestamps to reconstruct user activity:
      tail -500 ~/.zsh_history | while IFS= read -r line; do
        if echo "$line" | grep -q "^: [0-9]"; then
          ts=$(echo "$line" | sed 's/^: \([0-9]*\):.*/\1/')
          cmd=$(echo "$line" | sed 's/^: [0-9]*:[0-9]*;//')
          dt=$(date -r "$ts" "+%Y-%m-%d %H:%M:%S" 2>/dev/null)
          echo "$dt  $cmd"
        fi
      done
      
    • Filter to the time window around the incident.
  4. Identify all active agents/processes — check Claude Code session logs:

    ls -lt ~/.claude/projects/<project-dir>/*.jsonl | head -15
    

    Cross-reference modification times with the incident window.

Gate: Time window is established. List of active processes/sessions at the time is known.


Phase 2: System-Level Evidence (macOS Unified Log)

Run ALL of the following. Do not skip any — even if you expect empty results, the absence of evidence is evidence.

2a. Target process events
log show --start "<start>" --end "<end>" --style compact \
  --predicate 'process == "<target-process>"'

Replace <target-process> with the crashed process (e.g., "tmux", "tmux-server", "agent-dashboard"). Run for each relevant process name.

2b. Code signature / AMFI failures
log show --start "<start>" --end "<end>" --style compact \
  --predicate 'subsystem == "com.apple.AMFI" OR eventMessage CONTAINS "AMFI" OR eventMessage CONTAINS "code signature" OR eventMessage CONTAINS "CMS blob"'

Read the full file on GitHub · 249 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 249 lines · 30 tokens per session scan C 2d7ce2451e3e

Subscribe to this mod's changes

rca is a skill published in the GitHub repository bjornjee/agent-dashboard (26 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 2,484 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

rust-check

Run cargo check on the current Rust project to find compile errors.

Hmbown/CodeWhale · 15 tokens

debug

Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.

Hmbown/CodeWhale · 30 tokens

openrig-skills

Use when an agent running inside OpenRig needs the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also when the agent…

mvschwarz/openrig · 109 tokens

feedback

Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.

Hmbown/Codewhale · 0 tokens

oversight-team

Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…

mvschwarz/openrig · 117 tokens

developing-openrig

Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session runs on, judging whether a diff touches a high-risk area, or preparing a pull request. Not…

mvschwarz/openrig · 84 tokens