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 agentmods add skills/techtheist/engram/digestnpx skills add techtheist/engram --skill digestgit clone --depth 1 https://github.com/techtheist/engramWhat 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 | $0.00098 | $0.03096 |
| Opus 5 | $0.00049 | $0.01548 |
| Sonnet 5 | $0.00020 | $0.00619 |
| Haiku 4.5 | $0.00010 | $0.00310 |
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 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.
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 — 128 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.
2. Offline marker scan (tier 1). The daemon scans the tree for FIXME/TODO markers, gitignore-aware:
PORT=$(sed -n 's/.*"port"[: ]*\([0-9]*\).*/\1/p' .engram/daemon.json)
curl -s -X POST "http://127.0.0.1:${PORT}/digest/scan"
(No .engram/daemon.json or the health check fails → run engram-alpha serve from the repo root: it ensures the machine core is up, registers this repo, and exits on its own — no backgrounding. A 404 from /digest/scan means an older binary — engram-alpha update, then engram-alpha stop and engram-alpha serve to restart the core, retry once.)
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 First seen · 128 lines · 98 tokens per session scan A 428c76bb4688
engram-digest is a skill published in the GitHub repository techtheist/engram (17 stars, last pushed 3d ago), licensed MIT. It adds 98 tokens to every session and 3,096 once invoked, about $0.0005 per session on Opus 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
runaway-context
Use this skill when working in a project that has a RunawayContext v3 install. It loads the project's brief from the auto-generated Tier 3 markdown, queries knowledge.db for relevant lessons and chunks, and routes writes through the contract-enforced Client (HR-2 / HR-3 / HR-9). Trigger when the conversation enters a…
memory
Unified project memory management: update, prune, reflect, and maintain knowledge. Combines conversation scanning, deduplication, contradiction detection, confidence scoring, and consistency checks in a single skill. Usage: /memory update [topic] — scan conversation, persist learnings /memory prune [type] — find…
thoughtline-memory
Persistent, project-aware memory for AI coding agents. Use thoughtline whenever you make a decision, fix a bug, learn something non-obvious, or need to recall prior work.
design-is
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.