What is gitmem-hooks?

A GitMem hook plugin that manages the institutional-memory steps around coding-agent sessions. Hooks are automatic actions that run at selected points in a workflow.

Starting sessions automatically, reminding the agent to recall relevant history before consequential actions, and enforcing session closure.

It helps prevent sessions from starting without context, important actions from happening without recalling past decisions, or sessions from ending without proper closure.

gitmem-hooks — Plugin for Claude Code by gitmem-dev/gitmem

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/gitmem-dev/gitmem

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/plugins/gitmem-dev/gitmem/hooks/github.svg)](https://agentmods.dev/plugins/gitmem-dev/gitmem/hooks)

Your own site

<a href="https://agentmods.dev/plugins/gitmem-dev/gitmem/hooks"><img src="https://agentmods.dev/badge/plugins/gitmem-dev/gitmem/hooks/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.

Your own site · 80×15

<a href="https://agentmods.dev/plugins/gitmem-dev/gitmem/hooks"><img src="https://agentmods.dev/badge/plugins/gitmem-dev/gitmem/hooks.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 The manifest loads nothing itself; its 1 command, 5 hooks cost 12 tokens a session between them.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

gitmem-hooks 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 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

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.

hooks/.claude-plugin/plugin.json · 9 lines

What it actually says

{
  "name": "gitmem-hooks",
  "description": "Enforces the GitMem institutional memory lifecycle through hooks — auto-starts sessions, reminds you to recall before consequential actions, and ensures proper session closure.",
  "author": {
    "name": "nTEG Labs",
    "email": "[email protected]"
  }
}

Contents

What it installs

The manifest is a name and a version. 1 command, 5 hooks travel with it, and installing the plugin installs all of them — 12 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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.

1mo ago First seen · 9 lines scan A 1a3fac989416

Subscribe to this mod's changes

gitmem-hooks is a plugin published in the GitHub repository gitmem-dev/gitmem (9 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.

Claude Code Memory and context agentic-ai ai ai-agents institutional-memory mcp

hindsight-memory

Automatic long-term memory for Cursor via Hindsight. Recalls relevant memories before each prompt and retains conversation transcripts after each response.

vectorize-io/hindsight · not measured

agent-orchestration

Multi-agent system optimization, agent improvement workflows, and context management.

wshobson/agents · not measured

giovanni

AI Chief of Staff runtime: 4-layer memory with hard limits, daily digest with drift detection, stakeholder trajectories, invisible shadow hypotheses, adversarial-default review, and a governance lint that fails the build on contradictions. State lives in your repo; the mechanism lives here.

jaroslavsoucek-art/Giovanni · not measured

ejentum

Ejentum MCP server. Eight tools (four dynamic: reasoning, code, anti-deception, memory; four adaptive: adaptive-reasoning, adaptive-code, adaptive-anti-deception, adaptive-memory) that retrieve task-matched cognitive operations from a library of 679. Each operation is a structured procedure (numbered steps + failure…

ejentum/ejentum-mcp · not measured

aria-knowledge

ARIA — Applied Reasoning and Insight Architecture. Persistent human-governed knowledge for Claude Code via a five-phase lifecycle: capture → govern → promote → apply → refresh. Stages session insights/decisions/feedback into review backlogs, promotes approved items to a tag-indexed markdown base, and applies them via…

mikeprasad/aria-knowledge · not measured

aria-cowork

Knowledge management for Claude Cowork — capture, organize, and apply durable knowledge across your work, available in any project workspace via a persistent folder grant. Companion to aria-knowledge for Claude Code; both share one knowledge folder so insights flow between conversational and engineering work. Default…