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/ofershap/conversation-memory/historygit clone --depth 1 https://github.com/ofershap/conversation-memoryWhat 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.00009 | $0.00220 |
| Opus 5 | $0.00005 | $0.00110 |
| Sonnet 5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
history 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 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.
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
Display recent conversation history in a scannable format.
Use the conversation-memory skill for history file locations and search strategies.
Steps
-
Determine the AI tool:
- Claude Code: read
~/.claude/history.jsonl - Cursor: list
~/.cursor/projects/*/agent-transcripts/
- Claude Code: read
-
Get the most recent 10-15 conversations
-
For each conversation, show:
- Entry number
- Date/time in human-readable format (e.g., "Feb 18, 2026 15:30")
- Project name (just the folder name, not the full path)
- First 60-80 characters of the conversation topic
- Session ID or transcript UUID
-
Format as a plain text table with properly padded columns
-
At the end, include:
Tip: Use /recall <keyword> to search for a specific topic
Use /recall to get guided search options
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 · 33 lines · 9 tokens per session scan A a97e43221c4f
history is a command published in the GitHub repository ofershap/conversation-memory (1 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 220 once invoked, about $0.0000 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-31.
Other commands, from other repositories
sum
Distill insights from this conversation into memories.
search
Search Nowledge Mem for relevant memories.
save
Save current session to Nowledge Mem.
status
Check Nowledge Mem connection and server status.
nowledge-read-working-memory
Read today's Working Memory briefing.
import-history
Backfill older CodeBuddy sessions into Nowledge Mem Threads.