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.
npx skills add Zate/cc-plugins --skill cleanupgit clone --depth 1 https://github.com/Zate/cc-pluginsWrote 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/zate/cc-plugins/cleanup)<a href="https://agentmods.dev/skills/zate/cc-plugins/cleanup"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/cleanup/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/zate/cc-plugins/cleanup"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/cleanup.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.00069 | $0.01912 |
| Opus 5.5 | $0.00028 | $0.00765 |
| Sonnet 5.5 | $0.00014 | $0.00382 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
cleanup 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctx:cleanup — Memory Reconciliation
Reconcile Claude Code's built-in MEMORY.md system with the ctx knowledge graph. Detect duplicates, stale nodes, conflicts, and bloat across both systems, then resolve them with user approval.
Arguments
$1— Project name (optional, auto-detected from git)--global— Include all projects, not just the current one
Execution Flow
This is a phased command — run each phase in order, presenting findings to the user between phases.
Phase 1: Inventory
Gather the complete state of both memory systems.
Actions:
- Detect the current project name from git (
basename $(git rev-parse --show-toplevel)) - Run the analysis script to dump both systems:
sh "${CLAUDE_SKILL_DIR}/scripts/analyze-sync.sh" "$PROJECT" - Read the MEMORY.md file for this project from
~/.claude/projects/(search for directory matching project name) - Read any supplemental memory files (*.md besides MEMORY.md in the same directory)
- Query ctx for all project-scoped nodes:
ctx list --tag "project:$PROJECT" --format json - Query ctx for global nodes (no project tag or
project:global):ctx list --tag "project:global" --format json
If --global was passed, also inventory all other projects:
- List all directories in
~/.claude/projects/*/memory/ - List all unique
project:*tags in ctx viactx tags
Save the inventory mentally — it feeds all subsequent phases.
Phase 2: Analysis
Analyze the inventory for seven categories of issues. For each issue found, record: the issue type, affected items (node IDs / MEMORY.md line numbers), severity (high/medium/low), and recommended action.
Issue categories (consult references/sync-strategies.md for detailed detection patterns):
- Cross-system duplicates — Same knowledge in both MEMORY.md and ctx
- Compare MEMORY.md content against pinned/working ctx nodes
- Flag when semantically identical content exists in both
- Severity: medium
What ships with it
2 files beside SKILL.md 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.
- 1mo ago First seen · 198 lines · 69 tokens per session scan A 7e2299e99cfa
cleanup is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 1,912 once invoked, about $0.0003 per session on Opus 5.5. 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 skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.