What is add-telegram-swarm?

A feature that lets one Telegram group contain several agent identities, with each subagent speaking through its own bot name. Telegram is a messaging service, and a subagent is a helper agent working on part of a task.

Adding agent-team support to an existing Telegram channel, assigning pool bots to subagents, renaming them by role, and sending their messages to the group.

It makes team conversations easier to follow because members can see which role or agent sent each message.

add-telegram-swarm — Skill for Claude Code by sliamh11

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/sliamh11/Deus

agentmods

npx agentmods add skills/sliamh11/deus/add-telegram-swarm

Made for: Claude Code.

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/sliamh11/deus/add-telegram-swarm/github.svg)](https://agentmods.dev/skills/sliamh11/deus/add-telegram-swarm)

Your own site

<a href="https://agentmods.dev/skills/sliamh11/deus/add-telegram-swarm"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/add-telegram-swarm/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/sliamh11/deus/add-telegram-swarm"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/add-telegram-swarm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,632 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin 89% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.03632
Opus 5	$0.00032	$0.01816
Sonnet 5	$0.00013	$0.00726
Haiku 4.5	$0.00006	$0.00363

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

Security

Grade A, and why

add-telegram-swarm scanned grade A 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

1. Verify tokens: `curl -s "https://api.telegram.org/botTOKEN/getMe"`

Origin

This is a copy

89% identical to add-telegram-swarm — 41 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.

.claude/skills/add-telegram-swarm/SKILL.md · 386 lines

How it starts

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

Add Agent Swarm to Telegram

This skill adds Agent Teams (Swarm) support to an existing Telegram channel. Each subagent in a team gets its own bot identity in the Telegram group, so users can visually distinguish which agent is speaking.

Prerequisite: Telegram must already be set up via the /add-telegram skill. If src/telegram.ts does not exist or TELEGRAM_BOT_TOKEN is not configured, tell the user to run /add-telegram first.

How It Works

The main bot receives messages and sends lead agent responses (already set up by /add-telegram)
Pool bots are send-only — each gets a Grammy Api instance (no polling)
When a subagent calls send_message with a sender parameter, the host assigns a pool bot and renames it to match the sender's role
Messages appear in Telegram from different bot identities

Subagent calls send_message(text: "Found 3 results", sender: "Researcher")
  → MCP writes IPC file with sender field
  → Host IPC watcher picks it up
  → Assigns pool bot #2 to "Researcher" (round-robin, stable per-group)
  → Renames pool bot #2 to "Researcher" via setMyName
  → Sends message via pool bot #2's Api instance
  → Appears in Telegram from "Researcher" bot

Prerequisites

1. Create Pool Bots

Tell the user:

I need you to create 3-5 Telegram bots to use as the agent pool. These will be renamed dynamically to match agent roles.

Open Telegram and search for @BotFather

Send /newbot for each bot:

Give them any placeholder name (e.g., "Bot 1", "Bot 2")

Usernames like myproject_swarm_1_bot, myproject_swarm_2_bot, etc.

Copy all the tokens

Add all bots to your Telegram group(s) where you want agent teams

Wait for user to provide the tokens.

2. Disable Group Privacy for Pool Bots

Tell the user:

Important: Each pool bot needs Group Privacy disabled so it can send messages in groups.

For each pool bot in @BotFather:

Send /mybots and select the bot

Go to Bot Settings > Group Privacy > Turn off

Then add all pool bots to your Telegram group(s).

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

9d ago First seen · 386 lines · 64 tokens per session scan A 96627abc20b3

Subscribe to this mod's changes

add-telegram-swarm is a skill published in the GitHub repository sliamh11/Deus (51 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 3,632 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 89% identical to add-telegram-swarm, differing in 41 lines, and is treated as a copy.

Building agents Claude Code ai-assistant ai-memory persistent memory self-improving-ai semantic-memory

memcord

Privacy-first, self-hosted chat memory for OpenClaw — save and recall conversation history across sessions without any cloud dependency.

ukkit/memcord · 28 tokens

roadmap-build

Build or repair a roadmap that agents can actually execute, not just read. Produces a single validated YAML source of truth, generated views, definitions of done with evidence kinds, a task pool linked on two axes, an idea intake queue, and three standing checks that keep it honest. Use when asked to "build a…

datacore-one/datacore · 111 tokens

add-telegram-swarm