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 commands/techtheist/engram/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.00023 | $0.00190 |
| Opus 5 | $0.00012 | $0.00095 |
| Sonnet 5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
digest 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 3d 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.
What it actually says
The user wants this project digested into its Engram memory graph.
Invoke the engram-digest skill and follow it end to end: preflight the wiring, run the offline FIXME/TODO scan via the daemon's POST /digest/scan, read the project's reasoning surfaces, author nodes per the skill's worked examples under a single digest-<YYYY-MM-DD> session id, act on every write verdict, and finish with an audible summary plus a pointer to the pane.
If the engram MCP tools are not available in this session, stop and run /engram:setup first — never digest into an unwired repo.
$ARGUMENTS names a narrower scope (a directory or subsystem) when present; otherwise digest the whole working tree.
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.
- 3d ago First seen · 12 lines · 23 tokens per session scan A 87631560b2ff
digest is a command published in the GitHub repository techtheist/engram (17 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 190 once invoked, about $0.0001 per session on Opus 5. 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-30.
Other commands, from other repositories
tl-export
Export thoughtline memories to a markdown file the user can review or commit.
tl-search
Search thoughtline memories by keyword or topickey GLOB.
tl-ui
Tell the user how to open the thoughtline TUI dashboard.
tl-recent
Show the most recent thoughtline memories for the active project.
tl-stats
Summarize the thoughtline memory store for the active project.
encode-repo
Bootstrap a repository into Forgetful's knowledge base.