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/jasonhnd/life_os/inbox-processgit clone --depth 1 https://github.com/jasonhnd/life_OSWrote 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/jasonhnd/life_os/inbox-process)<a href="https://agentmods.dev/commands/jasonhnd/life_os/inbox-process"><img src="https://agentmods.dev/badge/commands/jasonhnd/life_os/inbox-process.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.00023 | $0.00572 |
| Opus 5 | $0.00012 | $0.00286 |
| Sonnet 5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
inbox-process 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 4d 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.
What it actually says
/inbox-process · Inbox ingest pipeline (v1.8.1 F3)
User invoked: /inbox-process $ARGUMENTS
What this does
Walks every *.md in meta/queue/to-process/ and proposes one of four
dispositions per item:
| Disposition | Action |
|---|---|
| accept | Write a new wiki/<domain>/<slug>.md entry per wiki/SCHEMA.md, append wiki/log.md (action=created), move source file to meta/queue/archive/ |
| update | Edit an existing wiki/<domain>/<slug>.md entry in place, append wiki/log.md (action=updated), move source file to meta/queue/archive/ |
| archive | Source has lasting reference value but doesn't merit a wiki entry; move to meta/queue/archive/ only |
| reject | One-off / no future value; move to meta/queue/archive/ and append wiki/log.md (action=rejected) |
| defer | Worth processing later; leave in to-process/ and add defer_until: YYYY-MM-DD to its frontmatter |
Backup mode
Slash command is backup mode. Primary path: user says "处理 inbox" /
"扫一下 inbox" / "process inbox"; ROUTER matches those phrases inline and
reads scripts/prompts/inbox-process.md. The slash command exists for
explicit invocation, focus narrowing, and audit/test.
Execution
Read and follow scripts/prompts/inbox-process.md step-by-step. That
prompt defines the full workflow (scan -> triage -> propose -> user-confirm
-> execute -> log). Do not invent your own flow.
If $ARGUMENTS is non-empty, treat it as a focus hint:
- domain name (
fintech,methodology) -> only process items that look like they belong to that domain wiki-> only propose accept/update; auto-defer anything ambiguousclean-> propose reject for any item older than 30 days that hasn't been touched
After execution, the user MUST see:
- A per-item disposition table with their accept/reject choices
- Counts (N accepted, M updated, K archived, L rejected, P deferred)
- Updated
wiki/log.mdexcerpt (last 10 lines) confirming entries landed
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.
- 4d ago First seen · 46 lines · 23 tokens per session scan A 234fb7b1fa59
inbox-process is a command published in the GitHub repository jasonhnd/life_OS (5 stars, last pushed 27d ago), licensed Apache-2.0. It adds 23 tokens to every session and 572 once invoked, about $0.0001 per session on Opus 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-31.
Other commands, from other repositories
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
full
Run the full hope pipeline — intent, shape, target, freeze as needed — then execute.
stoic-mode-commands
Activates, deactivates, and reports status of Stoic mode — a philosophical lens that adds Stoic depth to all system responses without changing analytical content.
output-commands
Reformatting, exporting, and comparing analysis outputs from skills and playbooks.
anvil
Start an adversarial debate to stress-test an idea.
anvil-cancel
Cancel an active Anvil debate.