message-send

A command for sending a text message from one Claude Code repository to another.

In plain words
What is it for?
Use it to send cross-repository updates or requests, with the first argument naming the destination and the remaining text forming the message.
Why use it?
It provides a consistent way to pass a recipient and multi-line message between separate repositories.

Command

Install

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.

agentmods
npx agentmods add commands/slima4/agent-message/message-send
Clone the repo
git clone --depth 1 https://github.com/slima4/agent-message
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 100 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00100
Opus 5 $0.00004 $0.00050
Sonnet 5 $0.00002 $0.00020
Haiku 4.5 $0.00001 $0.00010

Measured 2d ago against content hash fcf205165394, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

message-send 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 2d 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.

commands/message-send.md · 16 lines

What it actually says

$ARGUMENTS first word = <to>, rest = <body>. Run:

~/.agent-message-cmd send <to> <<'BODY'
<body>
BODY

Substitute <to> and <body> (preserve newlines/quotes — heredoc is single-quoted, no expansion).

Changes

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.

  1. 2d ago First seen · 16 lines · 8 tokens per session scan A fcf205165394

Subscribe to this mod's changes

message-send is a command published in the GitHub repository slima4/agent-message (18 stars, last pushed 24d ago), licensed MIT. It adds 8 tokens to every session and 100 once invoked, about $0.0000 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.