Borrowing it
Nothing to install: this file belongs to Lanzelot1/claw-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Lanzelot1/claw-brain/main/.claude/commands/process-inbox.mdgit clone --depth 1 https://github.com/Lanzelot1/claw-brainWrote 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/lanzelot1/claw-brain/process-inbox)<a href="https://agentmods.dev/commands/lanzelot1/claw-brain/process-inbox"><img src="https://agentmods.dev/badge/commands/lanzelot1/claw-brain/process-inbox/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/lanzelot1/claw-brain/process-inbox"><img src="https://agentmods.dev/badge/commands/lanzelot1/claw-brain/process-inbox.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.00008 | $0.00666 |
| Opus 5.5 | $0.00003 | $0.00266 |
| Sonnet 5.5 | $0.00002 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
process-inbox 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 2mo 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process all new files in the drop/ folder.
Steps
- Read
memory/_index.mdto discover all available areas - For each file in
drop/: a. Read the content and understand what it's about b. Archive original: Copy the file toraw/(prependYYYY-MM-DD-if no date prefix exists). Never overwrite — if a file with that name exists inraw/, append a counter. c. Categorize: Match it to an existing area from the index d. Prepare knowledge file:- If the file is already a well-structured
.mdwith frontmatter: move it toknowledge/{area}/, ensuresource:frontmatter exists, addtype: sourceif notype:field. - If the file is a PDF, image, data file, or unstructured text: create a new
.mdfile inknowledge/{area}/that extracts the key facts, data, and quotes. Setsource:to theraw/path. Settype: source. The raw file stays inraw/only. e. Checksource:frontmatter: If the source is unclear, ask the user: "Where did this file come from?" f. Cross-reference: Search other knowledge areas for substantively related files. If found, ask: "I found these related files — should I add cross-references?" If yes, add## Relatedsections with reciprocal links. g. Update wiki pages: Check if any existing wiki pages (type: wiki) inknowledge/cover topics related to this new source. If so, ask: "These wiki pages may need updating with the new information: [list]. Update them?" If yes, incorporate new facts and add the new source to their## Sourcessection. h. Add entries tomemory/_index.md(area section + Recently Added) i. Log: Append tomemory/log.md:YYYY-MM-DD HH:MM | ingest | {filename} → knowledge/{area}/{filename}
- If the file is already a well-structured
- If a file doesn't fit any existing area:
- Ask the user: "This file doesn't fit any existing area. Want to create a new one?"
- If yes, run the
/newworkflow first, then process the file into the new area
- Remove processed files from
drop/
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.
- 2mo ago First seen · 42 lines · 8 tokens per session scan A fc89ac14309f
process-inbox is a command published in the GitHub repository Lanzelot1/claw-brain (11 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 666 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
dashboard-session-unhide
Unhide a previously hidden session. Usage /dashboard:session-unhide.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
instinct-import
Import a portable YAML instinct pack with confidence-gated merge (Instinct Engine).
pop
Pop an item off the stash and continue working on it in the current session.