Development
Hook
Hooks
What inquisitor runs automatically, and when. A hook is a command Claude Code fires at a fixed moment, without you asking for it.
Install
> /plugin marketplace add 1111111111111111111114oLvT2/inquisitor > /plugin install inquisitor@inquisitor
Ships with inquisitor. Installing the plugin gets these hooks.
What fires, and when
SessionStart
Fires once when a session begins, and again after a context compaction. It is where a plugin sets up its environment, or restores state the compaction dropped.
- Matches
startup|resume|clear|compactnode "${CLAUDE_PLUGIN_ROOT}/hooks/inquisitor-core.js"
Where it lives
- hooks/inquisitor-core.jsRunsGitHub
Read the script
#!/usr/bin/env node // Inquisitor SessionStart hook: injects the always-on Core (skills/inquisitor/CORE.md) // as hidden session context — the lightweight triage router + gate. The full // 7-phase SKILL.md stays load-on-demand (CORE escalates to it only at Deep). // Best-effort: any failure exits 0 so a session never fails to start. const fs = require("fs"); const path = require("path"); let core; try { core = fs.readFileSync( path.join(__dirname, "..", "skills", "inquisitor", "CORE.md"), "utf8", ); } catch { process.exit(0); } process.stdout.write( JSON.stringify({ hookSpecificOutput: { hookEventName: "SessionStart", additionalContext: core, }, }), );
Read the script before you install anything that runs on your machine. This is the one part of a plugin that acts without being asked.
Ships withinquisitor
Hypothesis-driven problem solving for AI agents Probe · Falsify · Escalate — never overcomplicate, never blind-retry
Get the whole plugin

