agent-message

agent-message is a skill for Claude Code, Codex from gabrielmoreira/agent-skills-mirror. It costs 38 tokens per session (675 once invoked), scanned A, a copy of agent-message, MIT.

A messaging tool for sending direct text between related coding-agent sessions, such as a parent, sibling, or child agent. The system identifies the sender automatically.

In plain words
What is it for?
Use it to send instructions, updates, or requests to reachable parent, sibling, and child agents.
Why use it?
It lets agents coordinate without copying messages manually or pretending to be another agent.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to send instructions, updates, or requests to reachable parent, sibling, and child agents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gabrielmoreira/agent-skills-mirror/agent-message
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.

Any agent
npx skills add gabrielmoreira/agent-skills-mirror --skill agent-message
Clone the repo
git clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirror

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for agent-message

README.md
[![agentmods](https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/agent-message/github.svg)](https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/agent-message)
Your own site
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/agent-message"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/agent-message/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.

agentmods 80×15 button for agent-message

Your own site · 80×15
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/agent-message"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/agent-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 675 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00038 $0.00675
Opus 5.5 $0.00015 $0.00270
Sonnet 5.5 $0.00008 $0.00135
Haiku 4.5 $0.00004 $0.00068

Measured 9d ago against content hash 47cd188046db, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-message 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 9d 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.

Origin

This is a copy

100% identical to agent-message — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

mirrors/repos/7df-lab@claw-code-rust/crates/skills/assets/bundled/agent-message/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Message

Send direct messages within the current agent's nuclear family through the local daemon: parent, siblings, and direct children only. Roots are siblings of each other only when they share a parent worker; a root has no parent to message. The daemon derives your sender identity from the current session; do not try to include a from field.

Call directly from the kernel:

roster = await agent_observe.list_agents()
child = next(
    (
        item
        for item in roster.get("agents", [])
        if item.get("relationship") == "child"
    ),
    None,
)
if child is not None:
    receipt = await agent_message.send(
        "Please inspect the latest result.",
        receiver_role="child",
        receiver_name=child.get("sessionName") or child["sessionId"],
    )

API

  • await agent_observe.list_agents() (agent-observe skill) is the roster: it lists the parent, siblings, and children this skill can reach, active or not, with the relationship and sessionName that send takes as receiver_role and receiver_name.
  • await agent_message.send(message, receiver_role="parent" | "sibling" | "child", receiver_name=None) — sends one direct text message to one family member. Sending to an inactive or idle completed subagent wakes it and starts an ordinary follow-up turn in that same session and context. The child remains available only until its parent session closes. The daemon resolves receiver_role within the current agent family; receiver_name is required for siblings and children and omitted for the unique parent. send("all", message) broadcasts only to the family roster and returns {receipts: [...]} in roster order; successful entries are ordinary receipts and failed entries contain the target id and a short error. One failed delivery does not reject successful deliveries. Messages always use steering delivery so a busy target sees them during its active run. Returns a receipt with a deliveryStatus field: "delivered" means the message reached an idle target's context; "queued" means a steering message was accepted and will deliver when the target's current work allows (send does not block waiting for that). Delivered receipts carry deliveredAt, queued receipts carry queuedAt.

Read the full file on GitHub · 67 lines

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. 9d ago First seen · 67 lines · 38 tokens per session scan A 47cd188046db

Subscribe to this mod's changes

agent-message is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (19 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 675 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-message, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens