SessionStart

SessionStart is a hook for Claude Code from headroomlabs-ai/headroom. Its token cost is not measured, scanned A, original, Apache-2.0.

A session-start hook that runs when a coding-agent session starts or resumes.

In plain words
What is it for?
Use it to run `headroom init hook ensure` automatically on startup and resume.
Why use it?
It makes sure the Headroom startup setup command runs at the beginning of a session, without requiring you to run it yourself.

Hook for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the headroom plugin — 2 hooks shipped together

One of 2 entries in hooks.json upstream. Installing this one merges just its entry into your config; the other 1 are separate, each on its own page.

Good fit Use it to run headroom init hook ensure automatically on startup and resume.

Compare 6 hooks from other repositories ↓
About the project

Headroom is a library, proxy, and MCP server that compresses tool outputs, logs, files, retrieval chunks, and conversation history before they reach a language model. It helps coding agents use fewer context tokens while keeping the original content available locally when needed. Its catalogue add-ons support using Headroom with agent workflows.

headroomlabs-ai/headroom · 75,453 stars · on GitHub · docs.headroomlabs.ai

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add headroomlabs-ai/headroom
Claude Code
/plugin install headroom

Made for: Claude Code.

Or install headroom, the plugin that ships this one along with the rest of its 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for SessionStart

README.md
[![agentmods](https://agentmods.dev/badge/hooks/headroomlabs-ai/headroom/session-start/github.svg)](https://agentmods.dev/hooks/headroomlabs-ai/headroom/session-start)
Your own site
<a href="https://agentmods.dev/hooks/headroomlabs-ai/headroom/session-start"><img src="https://agentmods.dev/badge/hooks/headroomlabs-ai/headroom/session-start/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for SessionStart

Your own site · 80×15
<a href="https://agentmods.dev/hooks/headroomlabs-ai/headroom/session-start"><img src="https://agentmods.dev/badge/hooks/headroomlabs-ai/headroom/session-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 7 Sept 2026 📄 Read the review
Origin original No closer match found in the catalogue.
Security

Grade A, and why

SessionStart scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/headroom-agent-hooks/hooks/hooks.json · 15 lines

What it actually says

{
  "SessionStart": [
    {
      "matcher": "startup|resume",
      "hooks": [
        {
          "type": "command",
          "command": "sh -c '[ -n \"${CLAUDE_PLUGIN_ROOT:-}\" ] && launcher=\"${CLAUDE_PLUGIN_ROOT}/bin/headroom-hook.sh\" && [ -r \"$launcher\" ] && exec sh \"$launcher\"; exec headroom init hook ensure'",
          "powershell": "headroom init hook ensure",
          "timeout": 60
        }
      ]
    }
  ]
}
Same file

What else hooks.json configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago Changed · +1 lines c0d6badd3042
  2. 21d ago Changed 33f6c20ce123
  3. 1mo ago First seen · 14 lines scan A 8a935bc9c8fd

Subscribe to this mod's changes

SessionStart is a hook published in the GitHub repository headroomlabs-ai/headroom (75,453 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: a hook is shell that never enters the context. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.