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/engram-digestnpx skills add techtheist/engram --skill engram-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/engram-digest)<a href="https://agentmods.dev/skills/techtheist/engram/engram-digest"><img src="https://agentmods.dev/badge/skills/techtheist/engram/engram-digest.svg" alt="Measured on agentmods" 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 | $0.00098 | $0.03118 |
| Opus 5 | $0.00049 | $0.01559 |
| Sonnet 5 | $0.00020 | $0.00624 |
| Haiku 4.5 | $0.00010 | $0.00312 |
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 yesterday.
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" Copies of this mod
1 near-identical copy found in the catalogue:
- engram-digest — 100% identical, 0 lines differ
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.
- yesterday Changed c20c1c9410cd
- 5d ago First seen · 128 lines · 98 tokens per session scan A 428c76bb4688
engram-digest is a skill published in the GitHub repository techtheist/engram (18 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 3,118 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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…
curator-practice
Operating philosophy for autonomous memex curator tending — orientation protocol, signal triage, bounded work units, initiative thresholds, logging conventions. Trigger on cron-launched runs with no user prompt, "use your judgment", "tend without instructions", "do a pass on the vault", "I'll be away — do what needs…
recall
Retrieve session memory across 4 modes — TEMPORAL (date browsing), KEYWORD (FTS lookup), DEEP (cross-session synthesis), LOAD (specific file). Trigger on "what did I do yesterday/last week", "why did we...", "remind me...", "find the memo about...", "last time we...", "patterns across projects", "load the X topic". Do…
memo-writing
How to write effective session memos — format, frontmatter schema, observation extraction, topic-signal append. Trigger on /memex:save, "save this for later", "remember this", "save what we discussed", "document this session", "create a memo", or when the [memex] activity nudge appears in context. Do NOT trigger for…
health
Vault health audit — orphans, broken links, type-aware stale-review candidates, growth stats. Use whenever the user mentions vault maintenance, orphans, broken links, 'is my vault clean', 'проверь vault', 'сироты', 'битые ссылки', 'здоровье базы знаний', 'здоровье памяти', 'здоровье обсидиана', or asks for vault…
save
Use right after something worth keeping appears — you solved a tricky bug, made a non-obvious decision, hit a gotcha, or the user voiced a business rule, a pain, or how they think/decide — proactively, without being asked, so a future session doesn't relearn it. Also when the user says 'remember this', 'save this'…