Hook packs

Install portable hook packs.

Hook packs generate provider-native config for agent lifecycle telemetry and optional PreToolUse enforcement. They do not proxy model calls or ingest full transcripts.

Compile or install

Compile first when you want to inspect generated files. Install writes provider config into the current repository.

bash

verifier hook pack compile --provider claude-code,cursor,codex
verifier hook pack install --provider claude-code,cursor
verifier hook pack install --provider claude-code,cursor --mode enforce

Provider	Generated files
Claude Code	`.claude/settings.json`
Cursor	`.cursor/hooks.json`
Codex	`.codex/config.toml` and `.codex/hooks.json`

Telemetry mode

Lifecycle hooks call the verifier hook lifecycle command and emit signed hook events.

bash

verifier hook lifecycle <provider> <event>

Emits hook.completed or hook.failed records.
Carries provider, repository, developer, session, tool, matcher, duration, and hook status.
Carries hook pack profile metadata for portal provenance.
Fails open for telemetry-only capture so the developer workflow can continue.

Enforced mode

Enforced PreToolUse hooks call the guard command before the third-party tool executes.

bash

verifier hook guard <provider> PreToolUse

Blocking behavior

The guard evaluates sensitivity policy, requests portal approval for confirm decisions, emits hook.completed or hook.blocked, and exits with status 2 when the third-party tool call should be blocked.

Current limits

Keep the integration language exact when presenting hook packs to customers.

Claude Code lite activity connector is implemented, but live walkthrough remains pending.
Cursor lifecycle telemetry hooks are generated, but full activity logs, chat history, and edit-stream ingestion remain roadmap.
Copilot connector is not implemented.
Client-submitted cognitive-debt or drift scores are ignored unless the event source is trusted.