What is messaging-rules?

A reference guide for formatting and sending messages across Telegram, WhatsApp, Slack, and Discord. It explains each service's markup rules and when to include source links.

Preparing cross-channel messages, choosing the right bold, italic, bullet, code, heading, and link syntax, and adding source references when needed.

It prevents messages from using formatting that the destination service displays incorrectly. It also helps keep citations and links in the form expected by each channel.

messaging-rules — Skill for Claude Code and Codex by BreadchainCoop

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 BreadchainCoop/labor.fun --skill messaging-rules

Clone the repo

git clone --depth 1 https://github.com/BreadchainCoop/labor.fun

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/messaging-rules/github.svg)](https://agentmods.dev/skills/breadchaincoop/labor.fun/messaging-rules)

Your own site

<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/messaging-rules"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/messaging-rules/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/messaging-rules"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/messaging-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 879 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00879
Opus 5.5	$0.00014	$0.00352
Sonnet 5.5	$0.00007	$0.00176
Haiku 4.5	$0.00003	$0.00088

Measured 1mo ago against content hash fdcadeeab6c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

messaging-rules 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.

container/skills/messaging-rules/SKILL.md · 85 lines

How it starts

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

/messaging-rules — Communication Reference

How Breadbrich Engels formats and sends messages across channels.

Channel Formatting

Format based on the channel prefix in the group folder name:

Telegram (`telegram_`) / WhatsApp (`whatsapp_`)

*bold* (single asterisks, NEVER **double**)
_italic_ (underscores)
• bullet points
``` code blocks
No ## headings, no [links](url), no **double stars**

Slack (`slack_*`)

*bold* (single asterisks)
_italic_ (underscores)
<https://url|link text> for links (NOT [text](url))
• bullets (no numbered lists)
:emoji: shortcodes
> for block quotes
No ## headings — use *Bold text* instead

Discord (`discord_*`)

Standard Markdown: **bold**, *italic*, [links](url), # headings

Cite Your Sources

When an answer draws on a specific KB doc, web page, or GitHub/Linear item, end it with a compact channel-native Sources block (Slack <url|Title>, Telegram [Title](url), WhatsApp Title (url)). Skip for chit-chat. Deep-link internal docs into the KB dashboard when KB_DASHBOARD_URL is set. Full guidance: the citations skill and /workspace/project/rules/messaging/citations.md.

Communication Model

Standard output — returned text goes to the requesting channel
send_message MCP tool — sends immediately while still processing

Internal Thoughts

Wrap non-user-facing reasoning in <internal> tags — logged but not sent.

Cross-Channel Sending

Breadbrich Engels can send messages across platforms using target_jid:

Platform	JID Format	Example
Telegram user	`tg:USERID`	`tg:NNNNNNN`
Telegram group	`tg:-100GROUPID`	`tg:-100NNNNNNNN`
Slack channel	`slack:CHANNELID`	`slack:CXXXXXXXXX`
WhatsApp group	`[email protected]`	`[email protected]`

Permission Required

Any allowlisted user can cross-channel send
Unknown senders cannot

Person → JID Lookup

The authoritative roster of people-to-JID mappings lives in:

Read the full file on GitHub · 85 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.

1mo ago First seen · 85 lines · 34 tokens per session scan A fdcadeeab6c4

Subscribe to this mod's changes

messaging-rules is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 879 once invoked, about $0.0001 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-31.

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