Hook audit

Step 0: Gather context

Run Bash commands before proceed:

• ls "$(git rev-parse --show-toplevel 2>/dev/null)/.claude/hooks/"*.sh 2>/dev/null | wc -l -- installed hook scripts
• ls ~/.claude/hook-metrics/*.json 2>/dev/null | wc -l -- session summaries collected
• ls ~/.claude/hook-metrics/*.json 2>/dev/null | head -1 | xargs -I{} jq -r '.date' {} -- earliest date
• ls ~/.claude/hook-metrics/*.json 2>/dev/null | tail -1 | xargs -I{} jq -r '.date' {} -- latest date

Metrics dir: ~/.claude/hook-metrics/

Use /visual-plan for large action plans, /plan-arbiter for contradictory recommendations, and /agent-watchdog when auditing routine/agent-generated reports.

Your task

Analyze hook effectiveness across all session metrics. Read every JSON in ~/.claude/hook-metrics/. Produce report:

1. Hook activity