A project-memory system that stores decisions, reasons, cautions, problems, and insights in a durable graph. It is meant to preserve why a project works the way it does, not duplicate its code.

Use it to recall relevant project reasoning before substantial work and record important decisions, discoveries, and lessons for later sessions.

It prevents teams from repeatedly revisiting settled decisions or encountering known problems without their history. The guidance also stresses keeping stored memories accurate and useful.

engram — Skill for Claude Code and Codex by techtheist

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.

Any agent

npx skills add techtheist/engram --skill aggressive

Clone the repo

git clone --depth 1 https://github.com/techtheist/engram

Made for: Claude Code, Codex.

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/skills/techtheist/engram/aggressive/github.svg)](https://agentmods.dev/skills/techtheist/engram/aggressive)

Your own site

<a href="https://agentmods.dev/skills/techtheist/engram/aggressive"><img src="https://agentmods.dev/badge/skills/techtheist/engram/aggressive/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/skills/techtheist/engram/aggressive"><img src="https://agentmods.dev/badge/skills/techtheist/engram/aggressive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,947 The whole file, excluding the scripts and references it only reads on demand.

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

Origin 92% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00074	$0.02947
Opus 5.5	$0.00030	$0.01179
Sonnet 5.5	$0.00015	$0.00589
Haiku 4.5	$0.00007	$0.00295

Measured 2d ago against content hash f9dbd4728bda, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

engram 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 2d 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.

Origin

This is a copy

92% identical to engram — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/engram/aggressive/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engram — project memory (Aggressive)

Engram is a local, user-owned graph of why this project is the way it is: decisions and their reasons, gotchas, problems and their fixes, conventions. Not code structure — the code holds that. The user sees every node in the pane, so quality and honest edges matter more than volume: a noisy graph stops being trusted, and an untrusted graph stops being read.

Aggressive: Engram is the spine of the project's decision history. Every real decision, realization and gotcha belongs in the graph; err on the side of writing — decay prunes episodic scratch nobody re-confirms. Don't mirror Claude Code's own memory (CLAUDE.md, auto-memory): project reasoning goes to Engram, user preferences and workflow stay there.

Recall

Session start: read the brief. If the session opened with an injected "# Engram brief", that IS it; otherwise call brief once. Its first line names the graph — if that is not this workspace, call brief(project: "<workspace absolute path>").
Before any non-trivial decision, search. Read the confidence verdict (strong act / weak verify first / none say the graph is silent) and each hit's standing (contested and tombstone are said out loud; superseded → read the replacement). If a Decision or Caution covers what you're about to do, follow it or raise the contradiction with the user before acting.
On weak/none, reformulate before concluding absence: name the thing (entity-first), use the words a note would use, or scope in time (after: "last week", during_version). Pass time expressions as written; the daemon resolves them.
Start detail: "compact" when scanning; full only for hits you'll act on. get_node / traverse pull the reasoning around a hit; timeline walks a supersession chain; audit shows who changed what; list_open is the worklist; list_nodes is the lossless read for reviews and exports.
"Why is it like this?" → search, follow because/answers edges and timeline, retell as a short dated narrative.
Session history (if the user turned recording on): a weak verdict may carry a history section — leads, not knowledge. expand_history(session, turn) before relying on one; capture what matters as a proper note. list_sessions answers "what was I doing last Tuesday".

Read the full file on GitHub · 98 lines

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.

2d ago Changed · +13 lines f9dbd4728bda
6d ago Changed · -118 lines 295544433ae0
18d ago Changed a82bf096cef2
22d ago Changed · +1 lines 31243fd458da
28d ago Changed · +4 lines da0b6d33b37c
1mo ago Changed · +1 lines c687da85c1df
1mo ago First seen · 197 lines · 74 tokens per session scan A efde15f79967

Subscribe to this mod's changes

engram is a skill published in the GitHub repository techtheist/engram (32 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 2,947 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to engram, differing in 36 lines, and is treated as a copy.

Claude Code Memory Management Memory and context ai-memory ai-memory-system claude-code-plugin cli-tool

memory-protocol

A shared set of rules for using a persistent memory service across coding-agent sessions.

vbcherepanov/total-agent-memory · 120 tokens

memory

Activate this skill when starting a new session, beginning a new task, saving knowledge, recalling past decisions, or after completing significant work. Also activate on errors to log them for pattern analysis. Relevant when the user asks about memory, past context, lessons learned, decisions history, project…

vbcherepanov/total-agent-memory · 65 tokens

session-recap

Document Claude Code sessions by extracting knowledge into cross-referenced documentation. Triggers on "recap the session", "summarize the work", or after significant code changes.

sxhmilyoyo/sundayhao-plugins · 39 tokens

garden-tending

Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…

linxule/memex-plugin · 131 tokens

knowledge-bank-lookup

Delegates knowledge bank lookups to Explore subagents with reflections-first strategy that learns from past mistakes. Checks /reflections/ directory before documentation to extract documented failures to avoid and proven approaches to apply. Automatically triggers when user mentions services ([project-a], [project-b]…

sxhmilyoyo/sundayhao-plugins · 94 tokens

kb-ingest

Ingest external sources into the knowledge bank through interactive study or quick filing. Two modes — Quick (summarize → file) and Study (theme-by-theme deep dive with online research and personal notes → multi-layer KB output → optional blog/slack synthesis). Triggers on "ingest this", "study this article", "add to…

sxhmilyoyo/sundayhao-plugins · 152 tokens