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/skymanbp/cc-memoryWrote 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/plugins/skymanbp/cc-memory/cc-memory)<a href="https://agentmods.dev/plugins/skymanbp/cc-memory/cc-memory"><img src="https://agentmods.dev/badge/plugins/skymanbp/cc-memory/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/plugins/skymanbp/cc-memory/cc-memory"><img src="https://agentmods.dev/badge/plugins/skymanbp/cc-memory/cc-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 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.
What it actually says
{
"name": "cc-memory",
"version": "2.18.0",
"description": "Persistent memory for Claude Code — automatic save/restore across compactions and sessions. Anti-patch reconcile-on-write + LLM-judged semantic de-duplication, forced PROGRESS.md handoff with per-session annotation, live PLAN.md anchor, injection observability, FTS5 search, AI-judged extraction with Haiku + local Ollama fallback.",
"author": {
"name": "skymanbp",
"url": "https://github.com/skymanbp"
},
"homepage": "https://github.com/skymanbp/cc-memory",
"repository": "https://github.com/skymanbp/cc-memory",
"license": "MIT",
"keywords": [
"memory", "persistent-memory", "long-term-memory", "agent-memory",
"context-management", "context-window", "compaction", "session-handoff",
"claude-code", "claude-code-plugin", "anthropic", "llm-memory",
"mcp", "model-context-protocol", "hooks", "subagent",
"sqlite", "fts5", "full-text-search", "anti-patch", "plan", "directive"
],
"mcpServers": {
"cc-memory": {
"command": "python3",
"args": ["${CLAUDE_PLUGIN_ROOT}/cc_memory/mcp/server.py"]
}
}
}
What it installs
The manifest is a name and a version. 2 skills, 1 command, 2 agents, 5 hooks travel with it, and installing the plugin installs all of them — 260 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill save-memories A 38 tokens
- Skill ccm-load B 49 tokens
- Command cc-mem A 49 tokens
- Agent plan-refiner A 63 tokens
- Agent plan-guardian A 61 tokens
- Hook PreCompact A not measured
- Hook PostToolUse A not measured
- Hook SessionStart A not measured
- Hook Stop A not measured
- Hook UserPromptSubmit A not measured
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed b2a11daa2553
- 3d ago Changed ff29706c4609
- 14d ago Changed 4db82ee27526
- 22d ago Changed e65396bd757b
- 26d ago Changed 74129a96d191
- 28d ago Changed db3bf566bf1f
- 1mo ago Changed e82227287429
- 1mo ago Changed f80ebd5a9683
- 1mo ago First seen · 26 lines scan A a6ba4b202b98
cc-memory is a plugin published in the GitHub repository skymanbp/cc-memory (9 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
presence
Continuous-collaboration layer for Claude Code: living project model, outcome telemetry, event digest, and calibrated confidence. Fully local, install-once, applies to every project.
jarvis-os
A persistent memory hub for Claude Code that loads into every session from any directory, plus a curated set of research and workflow skills.
claimkeep
Continuous memory that survives context compaction — harvests your agent's own confidence-marked claims into a verbatim brief and re-injects it after compaction.
memsearch
Automatic semantic memory for Claude Code — remembers what you worked on across sessions.
recall
Durable, fully-local project memory for Claude Code. Logs every session to .recall/history.md and condenses it into .recall/context.md with a local Python summarizer (TF-IDF + TextRank) — no API key, no external model, nothing leaves your machine. New sessions resume from the saved context.
claude-code-hermit
Your own local Claude Tag, in the Claude app, Discord, Telegram, or a custom Claude Code channel.