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 skills/the-sid-dani/second-brain-os/inbox-processnpx skills add the-sid-dani/second-brain-os --skill inbox-processgit clone --depth 1 https://github.com/the-sid-dani/second-brain-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/skills/the-sid-dani/second-brain-os/inbox-process)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/inbox-process"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-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.00118 | $0.03945 |
| Opus 5 | $0.00059 | $0.01972 |
| Sonnet 5 | $0.00024 | $0.00789 |
| Haiku 4.5 | $0.00012 | $0.00394 |
Grade C, and why
inbox-process scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If `yes`: `rm -rf <path>` (folders need `-r`). How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
inbox-process
One intake surface for four related cleanup jobs: Inbox triage, unmigrated Projects triage, workspace-root audit, and a loose-file sweep of Desktop or Downloads. Every mode is propose-and-confirm; deletion receives its own explicit confirmation.
Before you begin: read the Configuration section in root CLAUDE.md. Path tokens like <workspace.inbox> resolve to whatever's defined there.
Why this exists
Two graveyard surfaces share the same triage shape:
-
0-Inbox/— capture zone. Items land fast (drag-drop, Drive download, paste). Without periodic triage, it graveyards. Research (§2 constraint #1) is unambiguous: surviving systems either skip Inbox entirely or have a discipline for clearing it.<user.name>kept Inbox per their README, so we need the discipline as a skill. -
Unmigrated
1-Projects/<slug>/folders (those missingCLAUDE.md) — folders placed in Projects without going through/new-project. Same disease: stuff dropped into the wrong location, never properly scaffolded, slowly accumulating. The workflow defect surfaced 2026-05-06 (9 of 12 Projects folders had no CLAUDE.md). Per SOUL Operating Principle "Capture before commit," these belonged in0-Inbox/until a deliberate decision to promote them — but absent a triage flow, they sat in1-Projects/unscaffolded.
These surfaces share the same triage flow: list candidates, inspect enough to route safely, show the full plan, confirm, then act. /prune-projects handles the next lifecycle stage (scaffolded projects that have gone stale).
/save-resource handles individual save-this-now operations. /inbox-process is the iteration wrapper that goes through everything weekly across both surfaces.
When to use
Trigger phrases (broad — over-trigger rather than miss):
- "process inbox" / "process my inbox"
- "Friday inbox review" / "Friday inbox" / "Friday cleanup"
- "what's in inbox?" / "what's in my inbox?"
- "clear my inbox" / "clean up inbox"
- "triage inbox" / "go through inbox"
- "inbox-process" / "/inbox-process"
- "clean up root" / "tidy the workspace root" / "what shouldn't be in root?"
- "organize my desktop" / "sort my screenshots" / "clean up downloads"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 278 lines · 118 tokens per session scan C a8692581a5ec
inbox-process is a skill published in the GitHub repository the-sid-dani/second-brain-os (2 stars, last pushed 28d ago), licensed MIT. It adds 118 tokens to every session and 3,945 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dr-fanout
One command to fan a Deep Research prompt out to several external LLMs at once (ChatGPT / Gemini / Grok / others) through the operator's logged-in browser, then collect the reports, archive the originals, and synthesize a consensus. Trigger on "/dr-fanout", "fan out the DR", "distribute the research prompt". Automates…
fb-reply
Read who commented on the owner's recent Facebook posts and post PERSONALIZED replies through their real logged-in Chrome (live-tab, low-ban-risk), draft-first and rate-limit-guarded. Trigger on "/fb-reply", "reply to my facebook comments". Replying on your OWN posts is expected behavior; the guard enforces a daily…
journey
Resurrect and continue a build-in-public BOOK — the serialized story of a founder + AI- cofounder journey. One command: pick up state (which days are written in which languages, what's uncommitted, where the gaps are), then continue writing via the established pipeline. Trigger on "/journey", "the book", "continue the…
3
Launch autonomous multi-machine consensus between Claude peers (hub + laptops + teammate machines): the peers negotiate a decision among themselves over a shared coordination channel and execute it, without using the human as a courier. Trigger on "/03" or phrases like "work it out among yourselves" / "find…
alfa-search-recall-deepresearch
Mandatory decision protocol ("Alpha Protocol") for any new STRATEGIC work — never jump to implementation on local recall alone. Run RECALL over the knowledge vault → GAP analysis → emit a DEEP RESEARCH PROMPT to run in external deep-research tools → SYNTHESIS + Decision Memo when results come back. Trigger on…
follower-onboard
Onboard a NEW family/team machine as a FOLLOWER-CONSUMER joining the multi-machine Claude+vault network. A follower READS the shared vault + canon + skills + memory as RECEIVE- ONLY data, runs nothing heavy locally (no RAG/reindex/GPU), and the hub never pushes executable hooks to it. Trigger on "/follower-onboard "…