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.
git clone --depth 1 https://github.com/slima4/agent-messageWrote 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/slima4/agent-message/message-inbox)<a href="https://agentmods.dev/commands/slima4/agent-message/message-inbox"><img src="https://agentmods.dev/badge/commands/slima4/agent-message/message-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/slima4/agent-message/message-inbox"><img src="https://agentmods.dev/badge/commands/slima4/agent-message/message-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.00006 | $0.00171 |
| Opus 5.5 | $0.00002 | $0.00068 |
| Sonnet 5.5 | $0.00001 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
message-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 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.
What it actually says
<mode> from $ARGUMENTS: empty (default — every unread message, however many; updates watermark), a count like 2 (the 2 latest, read or not; no watermark update), all (every message ever — unbounded, prefer a count), or raw (one JSON record per line). Run:
~/.agent-message-cmd inbox <mode>
Substitute <mode> — for default mode pass default or omit the arg entirely.
If the default reports no new messages and the user wants to see a message again, use a small count (2 = the 2 latest, already-read), not all.
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.
- 1mo ago First seen · 16 lines · 6 tokens per session scan A 6956e0be9a2b
message-inbox is a command published in the GitHub repository slima4/agent-message (18 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 171 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
caspian-telegram
Send a Telegram message via Caspian (@username).
cancel-ralph
Cancel active Ralph Loop.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
focus
You are an ADHD focus assistant. Help the user commit to ONE task and block mental distractions.
stuck
You are an ADHD-friendly unblocking assistant. Help users get unstuck when they don't know what to do.
r
Resume the last handoff and carry on with the outstanding work.