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 configgit 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/config)<a href="https://agentmods.dev/skills/llaa33219/casabot/config"><img src="https://agentmods.dev/badge/skills/llaa33219/casabot/config.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.1 | $0.00015 | $0.01400 |
| Opus 5 | $0.00008 | $0.00700 |
| Sonnet 5 | $0.00003 | $0.00280 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
CasAbot Configuration 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 7d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CasAbot Configuration
This manual explains CasAbot's directory structure, configuration file schema, and provider management methods.
1. Directory Structure
All CasAbot data is stored under ~/casabot/.
~/casabot/
├── casabot.json # All settings (providers, models, etc.)
├── skills/ # Skills directory (contains SKILL.md)
│ ├── agent/ # Agent creation & management
│ ├── config/ # Configuration management (this document)
│ ├── chat/ # Conversation management
│ ├── service/ # System service registration
│ ├── memory/ # Memory (memo) management
│ └── subskills/ # Sub-agent skill attachment and management
├── workspaces/ # Per-agent workspaces
│ └── <agent-name>/ # Individual agent working directory
│ └── output/ # Agent output results
├── history/ # Full conversation logs (raw logs, JSON)
└── memory/ # Agent-written memos (.md)
Role of Each Directory
| Directory | Description | Format |
|---|---|---|
casabot.json |
Provider settings, active model, and all configuration | JSON |
skills/ |
Skill manuals referenced by the base agent | SKILL.md (YAML + Markdown) |
workspaces/ |
Working spaces mounted to sub-agent containers | Free format |
history/ |
Auto-saved conversation logs (read-only) | JSON |
memory/ |
Memos written directly by agents | Markdown |
2. casabot.json Schema
Full structure of the configuration file.
{
"providers": [
{
"name": "provider name (unique identifier)",
"type": "openai | anthropic | huggingface | openrouter | custom-openai | custom-anthropic",
"apiKey": "API key",
"endpoint": "custom endpoint URL (optional, required for custom-* types)",
"model": "model name",
"isDefault": true
}
],
"activeProvider": "name of the currently active provider",
"baseModel": "base model name"
}
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.
- 7d ago First seen · 172 lines · 15 tokens per session scan A 98057937c906
CasAbot Configuration is a skill published in the GitHub repository llaa33219/casabot (5 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,400 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
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…
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.