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-reply)<a href="https://agentmods.dev/commands/slima4/agent-message/message-reply"><img src="https://agentmods.dev/badge/commands/slima4/agent-message/message-reply/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-reply"><img src="https://agentmods.dev/badge/commands/slima4/agent-message/message-reply.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.00009 | $0.00069 |
| Opus 5.5 | $0.00004 | $0.00028 |
| Sonnet 5.5 | $0.00002 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
message-reply 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.
What it actually says
Body = $ARGUMENTS. Run:
~/.agent-message-cmd reply <<'BODY'
<body>
BODY
Substitute <body> (preserve newlines/quotes).
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 · 16 lines · 9 tokens per session scan A bd560f7856df
message-reply is a command published in the GitHub repository slima4/agent-message (19 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 69 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.
message-reply compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| message-replyslima4/agent-message | Command | 19 | 2mo ago | MIT | A | 9 | Claude Code |
| caspian-telegramTryCaspian/caspian-sdk | Command | 970 | 2mo ago | AGPL-3.0 | A | 11 | Claude Code |
| cancel-ralphanthropics/claude-plugins-official | Command | 46k | yesterday | Apache-2.0 | A | 4 | Claude Code |
| engage.actionshypnguyen1209/offensive-claude | Command | 412 | 15d ago | MIT | A | 11 | Claude Code |
| focusData-Wise/claude-plugins | Command | 7 | yesterday | MIT | A | 0 | Claude Code |
| stuckData-Wise/claude-plugins | Command | 7 | yesterday | MIT | A | 0 | Claude Code |
| rao92265/claude-code-playbook | Command | 13 | 17d ago | MIT | A | 12 | Claude Code |