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/llaa33219/casabot/chatnpx skills add llaa33219/casabot --skill chatgit 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/chat)<a href="https://agentmods.dev/skills/llaa33219/casabot/chat"><img src="https://agentmods.dev/badge/skills/llaa33219/casabot/chat.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.00013 | $0.01173 |
| Opus 5 | $0.00006 | $0.00587 |
| Sonnet 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 5d 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.
- 5d 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 6mo 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. 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
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…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.