Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add skymanbp/cc-memory/plugin install 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/skills/skymanbp/cc-memory/ccm-load)<a href="https://agentmods.dev/skills/skymanbp/cc-memory/ccm-load"><img src="https://agentmods.dev/badge/skills/skymanbp/cc-memory/ccm-load/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/skills/skymanbp/cc-memory/ccm-load"><img src="https://agentmods.dev/badge/skills/skymanbp/cc-memory/ccm-load.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.00049 | $0.05141 |
| Opus 5.5 | $0.00020 | $0.02056 |
| Sonnet 5.5 | $0.00010 | $0.01028 |
| Haiku 4.5 | $0.00005 | $0.00514 |
Grade B, and why
ccm-load scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **marketplace / dev checkout** — `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccm-load — Load cc-memory into this project
Run this once in any new project to confirm cc-memory is active, the
project's .ccm/ is initialized, and PROGRESS.md/MEMORY.md are generated.
Idempotent — safe to re-run.
What this skill does
This skill covers activation and project bootstrap — the things no other
entry point does. Ongoing diagnostics belong to /cc-mem status; the two are
deliberately disjoint (see the table at the end of this file).
-
Verify activation, PER INSTALL LAYOUT. The two shipped layouts are activated by different mechanisms, so one check cannot serve both:
- marketplace / dev checkout —
~/.claude/settings.jsonenabledPluginsholds an enabledcc-memory@<marketplace>key (any marketplace name, ascli/mem.py:_marketplace_enabled_keymatches), root fromextraKnownMarketplaces.cc-memoryorplugins/installed_plugins.json(a/plugin marketplace add <github-repo>install has no local path), hooks declared by<root>/hooks/hooks.json. - standalone /
.exeinstaller — never appears inenabledPluginsat all.ui/installer.py:_merge_into_settingswrites only thehookskey, so activation meanssettings.json["hooks"]registers cc-memory for all five events; the tree it lays down is flat.
Either layout activated ⇒ proceed to bootstrap. Nothing activated ⇒ print the fix for the layout this machine actually has (never tell an
.exeuser to add a marketplace — they have no repo). The rule is mirrored fromcc_memory/cli/mem.py's_detect_install_layouts/_inspect_layout;/cc-mem statusreports the same layouts but never bootstraps, so this is the only entry point that gates project init on the verdict. - marketplace / dev checkout —
-
Resolve the installed package tree across both layouts (nested marketplace/dev checkout, flat standalone install) and fail loudly with actionable instructions if neither resolves.
-
Auto-initialize this project's
.ccm/— if.ccm/memory.dbis absent, create the directory tree + DB +.gitignore. (This also happens on first UserPromptSubmit; this skill makes it explicit.) -
Seed PROGRESS.md — write a current snapshot from the (possibly empty)
progressrow so the file exists from day one. -
Print quick DB counts (memories / sessions / topics / observations). This is not the
/cc-mem statushealth check — install-layout inspection, hook-registration verdicts, API-key resolution and last-save staleness all live there and are NOT run by this skill. -
Report status to the user in 1-2 sentences.
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.
- 3d ago Changed · +1 lines b71e9d3aebb2
- 14d ago Changed · +2 lines dc3dd03c26db
- 22d ago Changed · +1 lines cbae30032d05
- 1mo ago Changed · +1 lines 1ca0bbc4031a
- 1mo ago First seen · 382 lines · 49 tokens per session scan B 915cdf136705
ccm-load is a skill published in the GitHub repository skymanbp/cc-memory (9 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 5,141 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
knowledge-pack
Build a durable knowledge pack in the hub for one subject — a small always-read index plus numbered load-on-demand files, every claim sourced and graded. Use when the user says "build a knowledge pack", "make a reference on X", or when you notice you keep re-deriving or re-researching the same subject across sessions.
qmd
Vendored from tobi/qmd (github.com/tobi/qmd), npm package @tobilu/qmd, by Tobi Lutke. MIT License.
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
learn
Must be used near the end of any non-trivial turn that produced potentially reusable tools, guidance, errors, workarounds, or workflows, so those lessons are saved for future turns.
adapt-memory
Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable.
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.