Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tstockham96/claw-kitnpx agentmods add commands/tstockham96/claw-kit/reflectWrote 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/reflect)<a href="https://agentmods.dev/commands/tstockham96/claw-kit/reflect"><img src="https://agentmods.dev/badge/commands/tstockham96/claw-kit/reflect/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/commands/tstockham96/claw-kit/reflect"><img src="https://agentmods.dev/badge/commands/tstockham96/claw-kit/reflect.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.00000 | $0.00861 |
| Opus 5.5 | $0.00000 | $0.00344 |
| Sonnet 5.5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
reflect 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reflect
Curate and compress recent memory. This command reviews the last 7 days of journal entries, extracts durable insights, and updates long-term memory files. Think of it as memory maintenance -- moving important things from short-term to long-term storage.
Instructions
Step 1: Gather Recent History
Search for recent journal entries and activity using the search engine:
cd kit/search && npx tsx src/cli.ts search "journal session summary" --limit 20 --memory-path ../memory
Also read journal entries for the last 7 days directly. For each day from today back to 7 days ago, check if memory/journal/YYYY-MM-DD.md exists and read it if so. The search results may surface entries the direct reads miss, and vice versa.
Also read the current state of:
memory/long-term.mdmemory/preferences.mdmemory/learnings.mdmemory/projects/_index.md
Step 2: Extract Insights
From the journal entries and search results, identify:
-
Key facts that should be remembered long-term (decisions made, things learned, important context established). These go into
memory/long-term.md. -
Preference patterns -- things the user consistently does, prefers, or reacts to. If you notice something appearing more than once, or a clear preference emerging from behavior, it belongs in
memory/preferences.md. Only add genuine patterns, not one-off observations. -
Lessons learned -- mistakes that were made, corrections that were applied, or insights about what works and what doesn't. These go into
memory/learnings.md. -
Project status updates -- if projects had meaningful progress, update
memory/projects/_index.mdwith current status.
Step 3: Check for Duplicates via Search
Before adding each insight, search to see if it's already captured:
cd kit/search && npx tsx src/cli.ts search "key terms from the insight" --limit 3 --memory-path ../memory
Only add genuinely new information. If an existing entry needs updating, modify it rather than creating a duplicate.
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.
- 1mo ago First seen · 97 lines · 0 tokens per session scan A f362a7a48db0
reflect is a command published in the GitHub repository tstockham96/claw-kit (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 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
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).
help
Show how to use Penfield memory.
learn
Extract patterns and learnings from current session.
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.
log
View memory access log (reads, writes, deletes).
setup
Configure mnemonic for proactive memory operations.