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 xrgarcia/slashbin-ai-team --skill bot-stategit clone --depth 1 https://github.com/xrgarcia/slashbin-ai-teamWrote 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/xrgarcia/slashbin-ai-team/bot-state)<a href="https://agentmods.dev/skills/xrgarcia/slashbin-ai-team/bot-state"><img src="https://agentmods.dev/badge/skills/xrgarcia/slashbin-ai-team/bot-state/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/xrgarcia/slashbin-ai-team/bot-state"><img src="https://agentmods.dev/badge/skills/xrgarcia/slashbin-ai-team/bot-state.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.00056 | $0.00427 |
| Opus 5 | $0.00028 | $0.00214 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
bot-state 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 11d 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.
What it actually says
bot-state
Report this bot's resolved storage layout and what each location holds.
How to do it
Every path comes from the environment. Do not guess a path and do not hardcode one — the harness resolves these per bot and they move.
| variable | holds |
|---|---|
$BOT_STATE_DIR |
root of everything this bot remembers |
$BOT_SUMMARIES_DIR |
daily summary files, <date>-<channel>.md |
$BOT_ATTACHMENTS_DIR |
files people sent this bot |
$BOT_OUTBOX_DIR |
write a file here and it is attached to the reply |
$BOT_BUFFER_FILE |
rolling conversation buffer |
$BOT_SESSIONS_FILE |
per-channel session map |
$BOT_JOB_HISTORY_FILE |
scheduled job run history |
For each: report the resolved path, whether it exists, and a useful measure — file count for directories, size and last-modified for files.
If a variable is unset, say so plainly rather than substituting a guess. An unset variable means an older harness, not a missing directory.
Answer format
Lead with the state root, then a short table. Flag anything notable:
- a directory that does not exist yet (normal if the bot is new — say so)
- a state root inside a git working tree — fine for summaries, which are meant
to be reviewable, but attachments are arbitrary binaries and
git clean -xor a re-clone will take them - an empty summaries directory on a bot that has been running a while — that is a real problem worth naming, not a curiosity
Keep it short. This is a status answer, not an audit.
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.
- 11d ago First seen · 43 lines · 56 tokens per session scan A b3a252cbea52
bot-state is a skill published in the GitHub repository xrgarcia/slashbin-ai-team (11 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 427 once invoked, about $0.0003 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-30.
Other skills, from other repositories
brain-sync
Sync knowledge and learnings to the shared appie-brain repo. Every Appie commits with their own identity so contributions are traceable. Use after: complex tasks (5+ tool calls), significant discoveries, new skills, or client work. Fleet: Appie-1 (Orchestrator/MacMini), Appie-2 (CMO/DO), Appie-3 (CTO/VPS).
project-context-sync
Keep a living project state document updated after each commit, so any agent (or future session) can instantly understand where things stand.
memory-search
Search and retrieve information from the Appie brain — daily logs, project notes, decisions, topics, and long-term memory files stored in /.hermes/memory/. Use this skill whenever you need to recall past conversations, decisions, project context, personal preferences, or anything discussed previously.
hermes-dream
Nightly memory consolidation skill for Hermes agents (Appie-3 & Appie-4). Consolidates memory each night, writes to /hermes-dreams/, and delivers to fleet. Schedule: 03:10 AM daily via Hermes cron.
cognitive-memory
Implementation and troubleshooting of the Cognitive Memory (Cognify) system in Hermes Agent.
fleet-dream
Nightly memory consolidation across the Weblyfe agent fleet (Appie-1/2/5 OpenClaw + Appie-3/4 Hermes). Use when: running the nightly dream sweep, checking fleet memory status, or manually triggering consolidation. Collects memory from all fleet nodes, runs LLM analysis (MiniMax M2.7), and writes consolidated insights.