Check CCC's cross-session memory before building a feature or acting on "earlier work" claims.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
CCC indexes every session's commits, tickets, and transcripts across this
machine. Two `ccc` CLI verbs surface that index — use them instead of
re-deriving history from scratch or trusting an unverified claim in a prompt.
## Before building a feature
Run `ccc shipped "<feature description>"` first. It returns a verdict
(`shipped: true/false`), a confidence score, and evidence (repo, commit,
ticket) when true.
```bash
ccc shipped "csv export for dashboard tables"
```
- `shipped: true` with real evidence → don't rebuild it; go look at the
evidence and extend it instead.
- `shipped: false`, or `true` with thin/no evidence → treat it as unshipped
and proceed.
## When a task references earlier work
If a prompt or ticket says "like we did before", "the session that fixed X",
or otherwise assumes context you don't have, run `ccc recall "<query>"` to
find the session(s) it means.
```bash
ccc recall "csv export dashboard"
```
Each hit carries `session_id`, `title`, `repo`, `date`, and a `snippet` —
enough to decide whether to open the full transcript before acting.
## Two more verbs: file history and decisions
…
The line at the top of this page pins the label git:20261009.a664025, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (2634 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
amirfish1/claude-command-center · 197 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hse4rv7kanymsy4u
GET https://markdownregistry.com/api/v1/resolve?ref=amirfish1/claude-command-center/memory-recall
GET https://markdownregistry.com/api/v1/blob/fb60b87b1b6a3d274db5a67c9ee917f9a51acd15cd0939ffd0e5d3a1f145aca6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
amirfish1/claude-command-center · .agents/skills/testing-ccc-dashboard/SKILL.md · How to bring up and runtime-test the CCC dashboard (server.py) on a Linux box — ports, duplicate-instance bypass…
amirfish1/claude-command-center · .claude/skills/throughput/SKILL.md · Use when the user asks to open/show the CCC throughput (token) dashboard, or asks how many tokens they've used —…
amirfish1/claude-command-center · plugin/skills/a-b-copy/SKILL.md · Use when you want a marketing-copy A/B — spawns two writer sibling sessions via CCC that draft the SAME message…
amirfish1/claude-command-center · plugin/skills/bug-race/SKILL.md · Use when a bug has already survived at least one debugging attempt and you have 2-3 genuinely distinct root-cause…
amirfish1/claude-command-center · plugin/skills/ccc-orchestration/SKILL.md · Spawn, inject into, and ask questions of persistent sibling sessions via Claude Command Center (CCC).
amirfish1/claude-command-center · plugin/skills/docs-drift/SKILL.md · Use to catch documentation that has silently gone stale — it spawns ONE fresh sibling session via CCC that extracts…
amirfish1/claude-command-center · plugin/skills/dogfood/SKILL.md · Use for docs QA — it spawns ONE fresh sibling session via CCC that has never seen the feature, has it follow the README…
amirfish1/claude-command-center · plugin/skills/fleet-lane-dispatch/SKILL.md · Use when dispatching a batch of autonomous CCC worker lanes with a mission brief and a report_to return address, or…
amirfish1/claude-command-center · plugin/skills/fleet-verify/SKILL.md · Use after a UI or user-visible change and before you claim it works — it spawns ONE CCC verification lane that drives a…
zilliztech/memsearch · plugins/opencode/skills/memory-recall/SKILL.md · Search and recall relevant memories from past sessions via MemSearch. Use for past decisions, debugging notes, previous…
zilliztech/memsearch · plugins/codex/skills/memory-recall/SKILL.md · Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from…
zilliztech/memsearch · plugins/claude-code/skills/memory-recall/SKILL.md · Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from…
zilliztech/memsearch · plugins/openclaw/skills/memory-recall/SKILL.md · Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from…
papadopouloskyriakos/agentic-chatops · openclaw/skills/memory-recall/SKILL.md · Query OpenClaw's episodic memory — past triage outcomes, host patterns, alert history. Use before triage to check if…
evermind-ai/everme · plugins/kimicode/skills/memory-recall/SKILL.md · Session-start primer that tells Kimi how EverMe's automatic cross-session memory works and how to treat the injected…
