cross-channel-messaging

cross-channel-messaging is a skill for Claude Code, Codex from Peiiii/nextclaw. It costs 48 tokens per session (2,801 once invoked), scanned C, original, MIT.

A set of rules for deciding where an AI result should go: the current conversation, a later-reading inbox, or a chat channel such as Telegram or Weixin.

In plain words
What is it for?
It helps deliver reports, news briefings, recommendations, articles, notifications, and forwarded results across conversations and messaging channels.
Why use it?
It prevents results from being sent to the wrong place or being left only in the current chat when the user needs a notification or durable copy.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps deliver reports, news briefings, recommendations, articles, notifications, and forwarded results across conversations and messaging channels.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/peiiii/nextclaw/cross-channel-messaging
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 Peiiii/nextclaw --skill cross-channel-messaging
Clone the repo
git clone --depth 1 https://github.com/Peiiii/nextclaw

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 cross-channel-messaging

README.md
[![agentmods](https://agentmods.dev/badge/skills/peiiii/nextclaw/cross-channel-messaging/github.svg)](https://agentmods.dev/skills/peiiii/nextclaw/cross-channel-messaging)
Your own site
<a href="https://agentmods.dev/skills/peiiii/nextclaw/cross-channel-messaging"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/cross-channel-messaging/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 cross-channel-messaging

Your own site · 80×15
<a href="https://agentmods.dev/skills/peiiii/nextclaw/cross-channel-messaging"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/cross-channel-messaging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,801 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00048 $0.02801
Opus 5 $0.00024 $0.01401
Sonnet 5 $0.00010 $0.00560
Haiku 4.5 $0.00005 $0.00280

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

Security

Grade C, and why

cross-channel-messaging scanned grade C with 1 finding 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 10d 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.

Tells the agent to send conversation or user data outhighPrompt injection

An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.

- do not silently send back into the current session instead.
packages/nextclaw-core/src/features/agent/shared/skills/cross-channel-messaging/SKILL.md · 263 lines

How it starts

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

Result Delivery And Cross-Channel Messaging

This is a NextClaw built-in skill for the AI itself.

It teaches the AI how to choose among NextClaw's existing delivery primitives in a predictable way.

Use this skill when the user wants any of these:

  • send a result to another conversation,
  • deliver collected news, a briefing, report, recommendation, or article for later reading,
  • notify them through Weixin, Lark, Telegram, Signal, or another channel,
  • proactively send a message after a task finishes,
  • forward or relay content across sessions or channels.

Strong triggers include user wording such as:

  • "notify me when done",
  • "collect the news and send it to me",
  • "put this report somewhere I can read later",
  • "send this to my Weixin",
  • "message me on Telegram",
  • "forward the result to another chat",
  • "after you finish, send me a note elsewhere".

Do not wait for the user to name this skill. If the task is about delivery, routing, relaying, notifying, or proactive messaging, load this skill.

Core Rule

Pick the existing primitive that matches both the content shape and the destination:

  1. Reply in the current conversation: Just reply normally when the user means the current session.
  2. Deliver durable reading material: Use deliver_to_inbox for news digests, briefings, reports, recommendations, or articles meant to remain available for later reading and follow-up, unless the user explicitly names an external channel.
  3. Send to another conversation or channel: Use message when the user wants a direct outbound send to a specific channel/chat/account route. If an existing session may already hold the route, use sessions_list narrowly to recover that route first, then call message.

"Send it to me" or "notify me" alone is not an external route. Do not infer Weixin, Lark, Telegram, or another channel from saved configuration, a previous route, or the mere availability of message.

Tool Choice

Normal reply

Use a normal assistant reply when:

Read the full file on GitHub · 263 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. 10d ago First seen · 263 lines · 48 tokens per session scan C f2e809478035

Subscribe to this mod's changes

cross-channel-messaging is a skill published in the GitHub repository Peiiii/nextclaw (256 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,801 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.