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/TheLobbi/claudeWrote 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/thelobbi/claude/cc-memory)<a href="https://agentmods.dev/commands/thelobbi/claude/cc-memory"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/cc-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/thelobbi/claude/cc-memory"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/cc-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.00000 | $0.02703 |
| Opus 5.5 | $0.00000 | $0.01081 |
| Sonnet 5.5 | $0.00000 | $0.00541 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
cc-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 1mo 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cc-memory — Hybrid Memory Architecture for Claude Code
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
Usage
/cc-memory # Interactive setup
/cc-memory --init # Initialize split memory architecture
/cc-memory --status # Show memory usage, file sizes, token estimates
/cc-memory --rotate # Archive old session summaries
/cc-memory --audit # Check for bloat, duplicates, stale entries
/cc-memory --mcp # Set up MCP-backed persistent memory server
/cc-memory --dry-run # Show what would be created without writing
The Memory Problem
Claude Code provides MEMORY.md (first 200 lines loaded per session), but this has limits:
- 200-line cap: Only the first 200 lines are loaded — anything beyond is silently ignored
- Single file: Everything competes for space — project identity, preferences, decisions, patterns
- No semantic search: Claude can't query past memories, only read what's loaded
- No session continuity: Each session starts fresh with no awareness of what happened yesterday
The Solution: 3-Tier Memory Architecture
Tier 1: Split Rule Files (Always Loaded)
Files in .claude/rules/ are auto-loaded every session with no line limit per file.
Split memory by purpose instead of cramming into one MEMORY.md:
.claude/rules/
├── memory-profile.md # Project identity, team, domains
├── memory-preferences.md # User workflow preferences
├── memory-decisions.md # Architecture Decision Records
├── memory-patterns.md # Recurring code patterns & solutions
├── memory-sessions.md # Recent session summaries (rotated)
└── lessons-learned.md # Auto-captured errors and fixes
memory-profile.md
# Project Profile
- **Name**: {project_name}
- **Type**: {web app / API / CLI / library / monorepo}
- **Team**: {team_size, roles}
- **Domains**: {business domains}
- **Repo**: {repo_url}
- **Primary language**: {language}
- **Framework**: {framework}
- **Deploy target**: {cloud / on-prem / hybrid}
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.
- 1mo ago First seen · 353 lines · 0 tokens per session scan A ed8b51497257
cc-memory is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,703 tokens. 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
session-save
Save current session context for automatic resumption.