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.
git clone --depth 1 https://github.com/monoes/monomindWrote 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/monoes/monomind/session-memory)<a href="https://agentmods.dev/commands/monoes/monomind/session-memory"><img src="https://agentmods.dev/badge/commands/monoes/monomind/session-memory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/monoes/monomind/session-memory"><img src="https://agentmods.dev/badge/commands/monoes/monomind/session-memory.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00319 |
| Opus 5.5 | $0.00007 | $0.00128 |
| Sonnet 5.5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
automation:session-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 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.
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.
This is a copy
88% identical to session-memory — 55 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.
What it actually says
Cross-Session Memory
Purpose
Maintain context and learnings across Claude Code sessions for continuous improvement.
Memory Features
1. Automatic State Persistence
At session end, automatically saves:
- Active agents and specializations
- Task history and patterns
- Performance metrics
- Neural network weights
- Knowledge base updates
2. Session Restoration
// Restore a named session
mcp__monomind__session_restore({
sessionId: "sess-123"
})
Fallback with npx:
npx monomind hooks session-restore --id "sess-123"
3. Memory Types
Project Memory:
- File relationships
- Common edit patterns
- Testing approaches
- Build configurations
Agent Memory:
- Specialization levels
- Task success rates
- Optimization strategies
- Error patterns
Performance Memory:
- Bottleneck history
- Optimization results
- Token usage patterns
- Efficiency trends
4. Privacy & Control
// Check memory stats
mcp__monomind__memory_health({})
Manual control:
# List saved sessions
npx monomind session list
# Disable memory persistence
export MONOMIND_MEMORY_PERSIST=false
Benefits
- Contextual awareness
- Cumulative learning
- Faster task completion
- Personalized optimization
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 First seen · 73 lines · 18 tokens per session scan A 5bf3ee09cbc0
automation:session-memory is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 319 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to session-memory, differing in 55 lines, and is treated as a copy.
Other commands, from other repositories
claude-flow-memory
Interact with Claude-Flow memory system.
sessions
Manage OpenAI Codex session history, aliases, and session metadata.
checkpoint
Create an identified recovery point and inspect exact restoration differences.
recall
Retrieve scoped lessons and evaluate their assumptions, conflicts, and applicability.
save-session
Save current session state to a dated file in /.codex/session-data/ so work can be resumed in a future session with full context.
checklist
Generate a custom checklist for the current feature based on user requirements.