What the reviewer found
PostToolUse runs 13 LifeOS hooks from ~/.claude/hooks, including catch-all hooks (EventLogger.hook.ts, PostToolObserver.hook.ts, LoopDetector.hook.ts) of which EventLogger writes tool inputs, edit diffs and Bash output previews to ~/.claude/LIFEOS/MEMORY. Two go further: ConfigEvalFire.hook.ts spawns a behavioural eval on your Anthropic subscription whenever CLAUDE.md or a .hook.ts is edited (5-minute debounce), and CheckpointPerISC.hook.ts runs `git commit --no-verify` in repos you opt in via ~/.claude/checkpoint-repos.txt (empty by default).
broad-matcher— intercepts every tool calltelemetry— reports to a vendor
What was read
The hook definition and the 13 scripts it runs, fetched from danielmiessler/LifeOS:
LifeOS/install/hooks/hooks.jsonLifeOS/install/hooks/AgentInvocation.hook.tsLifeOS/install/hooks/Safety.hook.tsLifeOS/install/hooks/TabState.hook.tsLifeOS/install/hooks/ISAStaleWriteGuard.hook.tsLifeOS/install/hooks/ISASync.hook.tsLifeOS/install/hooks/CheckpointPerISC.hook.tsLifeOS/install/hooks/ConfigEvalFire.hook.tsLifeOS/install/hooks/AtlasEventCapture.hook.tsLifeOS/install/hooks/KnowledgeWriteGuard.hook.tsLifeOS/install/hooks/ComplexityRatchet.hook.tsLifeOS/install/hooks/EventLogger.hook.tsLifeOS/install/hooks/PostToolObserver.hook.tsLifeOS/install/hooks/LoopDetector.hook.ts
What the static scan said
The 26-rule scan found nothing in this file; the review read it anyway.
How this review was made
Fable 5.1 read the files above on 7 September 2026 and answered three questions: is it dangerous to whoever installs it, is each scanner finding real, and what should the installer know. The verdict is bound to the file's hash; when the file changes, it is scanned afresh and reviewed again. A script that changes while the definition does not is not re-reviewed — that is a known gap. How the scan and the review work.