Hooks & Settings Inspector
Visualize active hooks, registered mods, and configuration layers in real time from a reactive side pane or via /hooks-panel.
Optimize your reasoning context, audit uncommitted changes before exit, protect Git/Kubernetes environments, and run bias-free Cleanroom TDD in Claude Code CLI.
Zero telemetry. Your data stays on your device.
Optimized build, zero bloatware or lag.
Transparent open source code on GitHub.
Visualize active hooks, registered mods, and configuration layers in real time from a reactive side pane or via /hooks-panel.
Detects consecutive mechanical searches on the primary thread and prompts delegation to exploration subagents, preserving the main reasoning window.
Audits uncommitted Git changes, running Docker containers, and lingering background processes before closing the session via /checklist or upon exit.
Interactive banner above the prompt that surfaces blocking questions and notifications from concurrent background subagents with one-click actions.
Strict TDD guardrail preventing test-generating subagents from reading implementation source code, eradicating confirmation bias.
Enforces active GitHub CLI accounts per workspace directory and forbids bare kubectl mutations on production Kubernetes clusters without explicit context.
Interactive side pane and /hooks-panel command listing all configured hooks and active plugins.
Real-time gauge and circuit breaker counting consecutive mechanical searches to enforce subagent delegation.
Pre-exit safety inspector tracking uncommitted Git status, active Docker containers, and dangling tasks.
Inter-agent messaging inbox prioritizing blocking questions with quick action buttons.
Strict Double-Blind Cleanroom isolation for TDD subagents, preventing test data leakage.
Multi-profile guard aligning GitHub CLI accounts with workspaces and blocking un-scoped kubectl commands.
claude --plugin-dir mods/hooks-viewer --plugin-dir mods/undelegated-readsNo. All mods run inside Claude Code's official sandboxed ECMAScript runtime consuming exclusively the EngineInterface ($).
Yes. All environment resolution and system helpers are built for uniform cross-platform behavior and tested against automated suites.
Explore architectural trade-offs, technology stack, and key engineering learnings in the full Projects Hub case study.