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 llaa33219/casabot --skill memorygit clone --depth 1 https://github.com/llaa33219/casabotWrote 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/llaa33219/casabot/memory)<a href="https://agentmods.dev/skills/llaa33219/casabot/memory"><img src="https://agentmods.dev/badge/skills/llaa33219/casabot/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/skills/llaa33219/casabot/memory"><img src="https://agentmods.dev/badge/skills/llaa33219/casabot/memory.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.00014 | $0.01455 |
| Opus 5.5 | $0.00006 | $0.00582 |
| Sonnet 5.5 | $0.00003 | $0.00291 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade A, and why
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 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory
This manual explains the difference between History and Memory, and guides agents on how to write and query memos.
1. Difference between History and Memory
CasAbot has two storage systems. Make sure to use them correctly.
History — Conversation Logs
| Item | Description |
|---|---|
| Path | ~/casabot/history/ |
| Format | JSON |
| Author | System (auto-saved) |
| Editable | ❌ Read-only |
| Purpose | Raw logs of entire conversations |
| Contents | User input, agent responses, tool call results, etc. |
Memory — Agent Memos
| Item | Description |
|---|---|
| Path | ~/casabot/memory/ |
| Format | Markdown (.md) |
| Author | Agents (written directly) |
| Editable | ✅ Freely editable |
| Purpose | Record important information, learning outcomes, analysis results, etc. |
| Contents | Things agents need to remember |
Core Principles
- Never modify History. It is preserved as the original conversation log.
- Memory is freely written, modified, and deleted by agents. It is a space for organizing important information.
- When important information comes up in conversation, record it in Memory.
2. Memory File Location
~/casabot/memory/
├── 2024-01-15-project-analysis.md
├── 2024-01-16-server-setup.md
├── user-preferences.md
├── frequently-used-commands.md
└── ...
3. Writing Rules
Filename Rules
- With date (recommended):
YYYY-MM-DD-topic.md— Record at a specific point in time - Without date:
topic.md— Continuously updated record - Use alphanumeric characters and hyphens (
-) - Use hyphens instead of spaces
File Format
All memory files are written in Markdown (.md) format.
Recommended Content Structure
# Title
- **Author**: agent name
- **Date**: YYYY-MM-DD
- **Tags**: #keyword1 #keyword2
## Summary
One or two line summary of key content
## Details
Detailed content...
## Related Items
- Related memory filenames
- Related conversation IDs
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 · 246 lines · 14 tokens per session scan A ca89f6ab6d59
Memory is a skill published in the GitHub repository llaa33219/casabot (4 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,455 once invoked, about $0.0001 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.