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 agentmods add skills/kryptobaseddev/cleo/ct-memorynpx skills add kryptobaseddev/cleo --skill ct-memorygit clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/kryptobaseddev/cleo/ct-memory)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-memory"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-memory.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00571 |
| Opus 5 | $0.00009 | $0.00285 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
ct-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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ct-memory -- Brain Memory Protocol
Purpose
Ensures LLM agents never start conversations with amnesia. Provides structured memory access through CLEO's brain system using progressive disclosure.
Tier 0: Session Start (ALWAYS run on first interaction)
Use CLI (cleo) for all memory operations.
- The memory bridge (.cleo/memory-bridge.md) is already loaded via CLEO-INJECTION.md @-reference
- If the bridge content feels stale (>2 hours old), refresh:
cleo memory find "session task decision" --limit 10
- Check for anti-patterns to avoid:
cleo memory find "mistake error avoid warning" --limit 5
- If results are relevant, fetch details:
cleo memory fetch O-xxx O-yyy
Tier 1: During Work (run when topic-relevant)
Before Making Decisions
cleo memory find "decision ADR architecture" --limit 5- Check if a similar decision was already made
Before Repeating Work
cleo memory find "{current-topic}" --limit 10- Avoid re-doing work that's already been completed
After Completing Significant Work
cleo memory observe "Completed X using approach Y. Key learning: Z" --title "Work completion"
Anti-Hallucination Protocol
Before stating facts about the codebase or project:
- Search brain:
cleo memory find "{claim-topic}" --limit 5
- If results exist, verify your claim matches stored knowledge
- If no results, state your uncertainty clearly
Tier 2: Deep Recall (run when specifically needed)
Full Timeline
cleo memory timeline O-xxx --before 5 --after 5- Understand chronological context around a specific observation
Cross-Project Knowledge (via NEXUS)
cleo nexus search "pattern" --scope global- Search across all CLEO-managed projects
Token Budget Guidelines
| Operation | ~Tokens | When |
|---|---|---|
| memory-bridge.md (auto-loaded) | 200-400 | Always (free) |
cleo memory find |
50/hit | Discovery |
cleo memory fetch |
500/entry | Details |
cleo memory timeline |
200-500 | Context |
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 First seen · 78 lines · 18 tokens per session scan A 7624753c0e7d
ct-memory is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 15d ago), licensed MIT. It adds 18 tokens to every session and 571 once invoked, about $0.0001 per session on Opus 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-09-03.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…