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 commands/tstockham96/claw-kit/statusgit clone --depth 1 https://github.com/tstockham96/claw-kitWhat 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.00000 | $0.00610 |
| Opus 5 | $0.00000 | $0.00305 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
status 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/status
Show a comprehensive summary of everything the AI currently knows, plus the health of the search index. This is the "what do you know about me?" command.
Instructions
Step 1: Check Search Index Health
Run the search index status to get stats on indexed memory:
cd kit/search && npx tsx src/cli.ts status --memory-path ../memory
Note the number of chunks, files indexed, and when the index was last updated.
Step 2: Read Core Memory Files
Read the following files. If a file doesn't exist or is empty/unconfigured, note that section as "Not set up yet."
memory/identity.mdmemory/user.mdmemory/long-term.mdmemory/preferences.mdmemory/learnings.mdmemory/people/_index.mdmemory/projects/_index.mdmemory/journal/YYYY-MM-DD.md(today's date)
Step 3: Present Summary
Format the output as a clean, well-structured summary using this template:
## Status: Here's What I Know
### Search Index
- **Files indexed:** [N]
- **Chunks:** [N]
- **Last indexed:** [timestamp or "Never"]
- **Health:** [Good / Stale / Empty]
### My Identity
[Summarize identity.md -- name, personality, role. Or "Not configured yet."]
### About You
[Summarize user.md -- name, timezone, what they do, any context. Or "Not set up yet."]
### Key Facts
[List facts from long-term.md, or "No facts stored yet."]
### Your Preferences
[Summarize preferences.md -- communication, technical, work style. Or "No preferences recorded yet."]
### Lessons Learned
[Summarize learnings.md -- corrections and patterns. Or "No learnings recorded yet."]
### Active Projects
[List from projects/_index.md, or "No projects tracked yet."]
### Known People
[List from people/_index.md, or "No people recorded yet."]
### Recent Activity
[Summarize today's journal entry if it exists, or "No activity logged today."]
Formatting Rules
- Keep each section to 2-4 lines maximum. This is a summary, not a dump.
- If a section has many entries, show the 5 most recent and note how many more exist.
- Use bullet points for lists.
- The Search Index section should always appear first after the heading -- it tells the user whether memory retrieval is working.
- If the index is stale or empty, suggest running the indexer:
cd kit/search && npx tsx src/cli.ts index --memory-path ../memory - If most sections are empty, suggest that the user start populating memory with
/rememberor by running the setup process.
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.
- 2d ago First seen · 75 lines · 0 tokens per session scan A 72d04db8b913
status is a command published in the GitHub repository tstockham96/claw-kit (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 610 tokens. 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 commands, from other repositories
update-model
Change an OpenClaw model configuration — with mandatory discovery, provider-aware validation, and 5-step verification. Designed to prevent every class of model configuration error.
fleet-announce
Announce a fleet update to users — send a personalized message from each person's bot explaining what changed and why they should care.
fleet
Manage OpenClaw installations across multiple servers - assess state, push updates, notify users.
encode-repo
Bootstrap a repository into Forgetful's knowledge base.
everme-help
Print a concise EverMe plugin status + reference card.
merge_session
Merge session branch(es) into main via rebase + fast-forward push. Use from inside a session worktree pane to land your work, or with --all to batch merge all sessions from the main repo.