Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/llaa33219/casabotnpx agentmods add skills/llaa33219/casabot/chatWrote 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/chat)<a href="https://agentmods.dev/skills/llaa33219/casabot/chat"><img src="https://agentmods.dev/badge/skills/llaa33219/casabot/chat/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/chat"><img src="https://agentmods.dev/badge/skills/llaa33219/casabot/chat.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.00013 | $0.01173 |
| Opus 5.5 | $0.00005 | $0.00469 |
| Sonnet 5.5 | $0.00003 | $0.00235 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
Conversation Management 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 2mo 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conversation Management
This manual explains how to create, view, and search conversation sessions, and how to integrate with external services.
1. Session Management
Session Structure
Each conversation session is automatically saved as a JSON file in the ~/casabot/history/ directory.
{
"id": "unique session ID",
"startedAt": "2024-01-15T09:30:00.000Z",
"messages": [
{
"role": "user | assistant | system | tool",
"content": "message content",
"toolCalls": [],
"toolCallId": ""
}
]
}
Session Lifecycle
- Creation: A new session is automatically created when you run the
casabotcommand. - Persistence: Messages are automatically appended as the conversation progresses.
- Termination: The session closes when the program exits.
- Preservation: Logs are permanently preserved in the history directory after termination.
2. Loading Conversations
View recent conversation list
# Recent 20 conversations (newest first)
ls -lt ~/casabot/history/ | head -20
# Check filenames and sizes
ls -lhS ~/casabot/history/
View specific conversation
# View full conversation (formatted)
cat ~/casabot/history/<conversation-id>.json | jq '.messages[] | {role, content: .content[:100]}'
# View only user messages
cat ~/casabot/history/<conversation-id>.json | jq '.messages[] | select(.role == "user") | .content'
# View only assistant responses
cat ~/casabot/history/<conversation-id>.json | jq '.messages[] | select(.role == "assistant") | .content'
Check session metadata
# Session ID and start time
cat ~/casabot/history/<conversation-id>.json | jq '{id, startedAt, messageCount: (.messages | length)}'
3. Searching Previous Conversations
Search by keyword
# Search all conversations for a keyword
grep -rl "keyword" ~/casabot/history/
# View context of conversations containing the keyword
grep -l "keyword" ~/casabot/history/*.json | while read f; do
echo "=== $(basename $f) ==="
cat "$f" | jq '.messages[] | select(.content | contains("keyword")) | {role, content: .content[:200]}'
done
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.
- 2mo ago First seen · 166 lines · 13 tokens per session scan A a2f61802d791
Conversation Management is a skill published in the GitHub repository llaa33219/casabot (5 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,173 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.
Conversation Management compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Conversation Managementllaa33219/casabot | Skill | 5 | 8mo ago | Apache-2.0 | A | 13 | Claude Code, Codex |
| orbit-notionnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 117 | Claude Code, Codex |
| agentmailpaperclipai/paperclip | Skill | 111k | yesterday | MIT | A | 30 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 184 | Claude Code |
| rowboat-spacesrowboatlabs/rowboat | Skill | 18k | yesterday | Apache-2.0 | A | 60 | Claude Code, Codex |
| feishuHmbown/CodeWhale | Skill | 41k | 6d ago | MIT | A | 33 | Claude Code, Codex |
| pinchtab-mcppinchtab/pinchtab | Skill | 11k | 10d ago | MIT | A | 52 | Claude Code, Codex |