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/thesmokedev/taskchad-os/prime-memorygit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/commands/thesmokedev/taskchad-os/prime-memory)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/prime-memory"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/prime-memory.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.00024 | $0.00806 |
| Opus 5 | $0.00012 | $0.00403 |
| Sonnet 5 | $0.00005 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
prime-memory 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prime: Memory Pipelines Slice
Objective
Build understanding of the 5 automated memory pipelines that keep The Homie's memory current: heartbeat, daily reflection, weekly synthesis, dream consolidation, and session flush. Plus the search/indexing layer, working memory (Living Mind), and episodes (autobiography).
Key Files to Read
Read these files in order. Pipelines live in .claude/scripts/; search and support modules are alongside them.
Architecture doc (read first)
@.claude/sections/03_memory_pipelines.md
Config and shared state
@.claude/scripts/config.py @.claude/scripts/shared.py
Heartbeat (every 30 min)
@.claude/scripts/heartbeat.py
Daily reflection (8 AM)
@.claude/scripts/memory_reflect.py
Weekly synthesis (Sunday 8 PM)
@.claude/scripts/memory_weekly.py
Dream consolidation (post-weekly + standalone)
@.claude/scripts/memory_dream.py
Session flush (on session end / pre-compact)
@.claude/scripts/memory_flush.py
Search and indexing
@.claude/scripts/memory_search.py @.claude/scripts/memory_index.py @.claude/scripts/db.py
Identity payload reader (shared shim)
@.claude/chat/cognition/identity_payload.py
Working memory (Living Mind Phase 1)
@.claude/scripts/living_memory.py
Episodes (Living Mind Act 3)
@.claude/scripts/episodes.py
Entity compilation engine
@.claude/scripts/entity_extractor.py
Slice Boundaries
- Owns: heartbeat gather+reason, daily reflection, weekly synthesis, dream consolidation (4 phases), session flush, memory search (keyword/semantic/hybrid), markdown indexing, working memory CRUD, episode write/consolidate, entity extraction+compilation
- Does NOT own: recall pipeline (
.claude/chat/cognition/recall.py— see/prime-signal), chat routing, runtime provider selection, vault structure (canonical memory lives invault/memory/) - Cross-slice touchpoints: all pipelines use
run_with_fallback()from runtime for LLM calls; reflection/synthesis call entity compilation post-step; dream reads episodes; flush writes episodes; heartbeat writes working-memory observations
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.
- 5d ago First seen · 88 lines · 24 tokens per session scan A ebc432d5eaae
prime-memory is a command published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 806 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
ov
Show OpenViking memory plugin status — server, identity, last injection / recall, toggles.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.
compass-verify
Verify the Merkle hash chain over /.claude/projects/ /memory/ and report any tampered or missing files.