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/alivecontext/alive/alive-inboxnpx skills add alivecontext/alive --skill alive-inboxgit clone --depth 1 https://github.com/alivecontext/aliveWrote 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/alivecontext/alive/alive-inbox)<a href="https://agentmods.dev/skills/alivecontext/alive/alive-inbox"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-inbox.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.1 | $0.00018 | $0.00396 |
| Opus 5 | $0.00009 | $0.00198 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
alive-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 6d 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 Scanner
Check 03_Inbox/ for files that need routing.
Process
- List all files in
03_Inbox/:
find "$ALIVE_WORLD_ROOT/03_Inbox" -type f -not -name ".*" -not -name "*.DS_Store" 2>/dev/null
-
For each file:
- Read the first 500 chars to understand content
- Suggest a destination walnut based on content
- Classify type (document, transcript, screenshot, data)
-
Present grouped by suggested destination:
Inbox: [N] files
[walnut-name]:
1. [filename] -- [type] -- [one-line description]
2. [filename] -- [type] -- [one-line description]
[other-walnut]:
3. [filename] -- [type] -- [one-line description]
Unsure:
4. [filename] -- [content preview]
Reply with numbers to approve routing. "all" to approve all. "skip" to leave for later.
Rules
- If inbox is empty, output
[SILENT] - Don't move files -- just suggest. Wait for approval.
- Files older than 48 hours get flagged: "This has been in inbox for [N] days"
- Max 10 files per notification. If more, show count and suggest
/alive-capture
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.
- 6d ago First seen · 57 lines · 18 tokens per session scan A 0c6cd6fed5d5
alive-inbox is a skill published in the GitHub repository alivecontext/alive (127 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 396 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-30.
Other skills, from other repositories
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
brain-log
Show brain sync and evolution history.
writing-handoff
Use when an auto-compaction system reminder appears, when the user explicitly invokes /handoff or asks to "write a handoff" / "save state", or when the user signals they're near the context limit specifically ("running low on context", "almost out of context", "context is getting full"). Do NOT fire on general…
crit-story
Author a crit story only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
mnemon
Persistent graph-based memory. Recall context before responding, remember insights after. Each group has private memory; global memory is read-only.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.