status

status is a command for Claude Code from tstockham96/claw-kit. It costs 0 tokens per session (610 once invoked), scanned A, original, MIT.

A command that summarizes what the AI knows about the user and checks the health of its searchable memory index.

In plain words
What is it for?
Use it to inspect stored identity, preferences, projects, recent activity, and index status.
Why use it?
It makes missing, outdated, or unconfigured memory visible instead of leaving the assistant's context uncertain.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is cd kit/search && npx tsx src/cli.ts status --memory-path ../memory.

Good fit Use it to inspect stored identity, preferences, projects, recent activity, and index status.

Compare 6 commands from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/tstockham96/claw-kit
agentmods
npx agentmods add commands/tstockham96/claw-kit/status

Made for: Claude Code.

Wrote 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.

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/commands/tstockham96/claw-kit/status/github.svg)](https://agentmods.dev/commands/tstockham96/claw-kit/status)
Your own site
<a href="https://agentmods.dev/commands/tstockham96/claw-kit/status"><img src="https://agentmods.dev/badge/commands/tstockham96/claw-kit/status/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.

agentmods 80×15 button for status

Your own site · 80×15
<a href="https://agentmods.dev/commands/tstockham96/claw-kit/status"><img src="https://agentmods.dev/badge/commands/tstockham96/claw-kit/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 610 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00610
Opus 5.5 $0.00000 $0.00244
Sonnet 5.5 $0.00000 $0.00122
Haiku 4.5 $0.00000 $0.00061

Measured 1mo ago against content hash 72d04db8b913, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

kit/commands/status.md · 75 lines

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."

  1. memory/identity.md
  2. memory/user.md
  3. memory/long-term.md
  4. memory/preferences.md
  5. memory/learnings.md
  6. memory/people/_index.md
  7. memory/projects/_index.md
  8. memory/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 /remember or by running the setup process.

Read the full file on GitHub · 75 lines

Changes

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.

  1. 1mo ago First seen · 75 lines · 0 tokens per session scan A 72d04db8b913

Subscribe to this mod's changes

status 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 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.