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.
npx skills add techtheist/engram --skill digestgit clone --depth 1 https://github.com/techtheist/engramWrote 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.
[](https://agentmods.dev/skills/techtheist/engram/digest)<a href="https://agentmods.dev/skills/techtheist/engram/digest"><img src="https://agentmods.dev/badge/skills/techtheist/engram/digest/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.
<a href="https://agentmods.dev/skills/techtheist/engram/digest"><img src="https://agentmods.dev/badge/skills/techtheist/engram/digest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00098 | $0.03298 |
| Opus 5.5 | $0.00039 | $0.01319 |
| Sonnet 5.5 | $0.00020 | $0.00660 |
| Haiku 4.5 | $0.00010 | $0.00330 |
Grade A, and why
engram-digest scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "http://127.0.0.1:${PORT}/digest/scan" This is a copy
100% identical to engram-digest — 0 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engram digest — ingest an existing project
Digestion turns a codebase that predates its memory graph into a first graph. It is explicit and opt-in: it runs only when the user asks, never automatically. One digestion is a bounded pass, audibly reported at the end — the opposite of the engram skill's silent trickle capture.
The target is the current working tree — the code and docs that exist now on this branch. Git history is supporting material only (the why behind what you see), never a deep crawl of old commits. And Engram is reasoning memory, not a code map: digest the decisions, constraints, and gotchas the code embodies — not its structure, which the code itself already records. Quality over coverage; a good first digest is dozens of well-linked nodes, not hundreds of thin ones.
Procedure
0. Preflight. The engram MCP tools must be available (if not, the repo isn't wired — run engram-alpha setup, or the plugin's /engram:setup, and stop). Agree the scope with the user if they gave one ("just the backend"); default is the whole tree. A near-empty tree (fresh scaffold, no docs, no real code) has nothing to digest — say so and stop; never pad a graph to have something to show. Choose the ingest session id now: digest-<YYYY-MM-DD> — every write in this pass carries it (see Session marking).
1. Recall first. Call brief (or read the injected one). If the graph already has nodes, digestion tops up: search each area before writing about it, and lean on the dupe guard — never re-state what the graph already holds.
1b. Choose the shape before the first write. A digest pours dozens of nodes into whatever ontology the graph has, so review the settings with the user first: GET /projects/<name>/config on the core (the manual is GET /guide — read it once), then ask whether the shipped 9-type set fits this project, or whether a preset (research, minimal, general) or a custom ontology fits better, and whether custom fields should carry what the user would otherwise repeat in every body (an owner, a component, a ticket, an effective date). If anything is customized: PUT /config per the guide, set brief.ontology.show = true so every later session learns the vocabulary, reinstall the skill (POST /skills/install), and translate the examples below into that vocabulary. The user decides; you propose.
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 Changed · +2 lines b6db305e60f1
- 1mo ago Changed c20c1c9410cd
- 1mo ago First seen · 128 lines · 98 tokens per session scan A 428c76bb4688
engram-digest is a skill published in the GitHub repository techtheist/engram (32 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 3,298 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to engram-digest, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
memory-protocol
A shared set of rules for using a persistent memory service across coding-agent sessions.
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…
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.
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…
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]…
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…