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/briefinggit clone --depth 1 https://github.com/tstockham96/claw-kitWrote 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/commands/tstockham96/claw-kit/briefing)<a href="https://agentmods.dev/commands/tstockham96/claw-kit/briefing"><img src="https://agentmods.dev/badge/commands/tstockham96/claw-kit/briefing.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.00000 | $0.00803 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
briefing 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 3d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/briefing
Morning summary. Show the user where things stand so they can pick up where they left off. This is the "catch me up" command.
Instructions
Step 1: Gather Context
Read the following files directly (skip any that don't exist):
memory/journal/YYYY-MM-DD.md-- today's date (may not exist if it's early in the day)memory/journal/YYYY-MM-DD.md-- yesterday's datememory/journal/YYYY-MM-DD.md-- two days ago (for additional context if yesterday is thin)memory/projects/_index.md-- active projectsmemory/people/_index.md-- known people for contextmemory/user.md-- for timezone and personal context
Step 2: Search for Recent Activity
Use the search engine to find recent activity, decisions, and context that the direct file reads might miss:
cd kit/search && npx tsx src/cli.ts search "recent session work progress" --limit 10 --memory-path ../memory
Also search for any active project names found in projects/_index.md to surface recent project-specific context:
cd kit/search && npx tsx src/cli.ts search "[project name]" --limit 5 --memory-path ../memory
Scan the decisions directory for any files from the last 7 days:
memory/decisions/-- look for files with recent dates in their filenames
Step 3: Search for People in Context
If any people were mentioned in recent journal entries or search results, search for additional context:
cd kit/search && npx tsx src/cli.ts search "[person name]" --limit 3 --memory-path ../memory
Step 4: Build the Briefing
Present a clean, scannable summary using this format:
## Good morning. Here's where we left off.
### Last Session
[Summarize the most recent journal entry. What was worked on? What was the state when the session ended? Any open threads?]
[Include citations: (Source: journal/YYYY-MM-DD.md#line)]
[If no recent journal entries exist: "No recent session history. This might be our first conversation, or sessions haven't been logged yet."]
### Active Projects
[For each project in _index.md, show: name, current status, and any recent activity from journal entries or search results. Highlight anything that seems urgent or time-sensitive.]
[Include citations to project files and journal entries.]
[If no projects: "No projects being tracked yet."]
### Recent Decisions
[List any decisions from the last 7 days with a one-line summary of each. Include citation to decision file.]
[If none: skip this section entirely.]
### Open Threads
[Extract any unresolved questions, pending items, or "next steps" mentioned in recent journal entries or search results. These are things that might need attention today.]
[If none: skip this section entirely.]
### People in Context
[If any people were mentioned in recent journal entries, note them briefly with their role/relationship. Include citations.]
[If none: skip this section entirely.]
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.
- 3d ago First seen · 85 lines · 0 tokens per session scan A 744959b3209a
briefing 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 803 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.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
everme-help
Print a concise EverMe plugin status + reference card.