ghostclaw: Skill for Claude Code

.claude/skills/add-telegram-swarm/SKILL.md

add-telegram-swarm is a skill for Claude Code from b1rdmania/ghostclaw. It costs 64 tokens per session (3,630 once invoked), scanned A, a copy of add-telegram-swarm, MIT.

A way to run a team of agents in a Telegram group, with each subagent appearing as a separate bot identity. Telegram is a messaging service; this requires an existing Telegram channel setup.

In plain words
What is it for?
Showing messages from roles such as a researcher as distinct Telegram bots, while the main bot receives the group’s messages and coordinates responses.
Why use it?
It makes it clear which subagent is speaking when several agents work together. Without it, their messages would appear under the main bot.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions subagents.

This is b1rdmania/ghostclaw's own configuration. It tells Claude Code how to work on ghostclaw itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ghostclaw configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./container/build.sh # Required — MCP tool changed.

Reuse

Borrowing it

Nothing to install: this file belongs to b1rdmania/ghostclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/b1rdmania/ghostclaw/main/.claude/skills/add-telegram-swarm/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/b1rdmania/ghostclaw

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.

agentmods badge for add-telegram-swarm

README.md
[![agentmods](https://agentmods.dev/badge/skills/b1rdmania/ghostclaw/add-telegram-swarm/github.svg)](https://agentmods.dev/skills/b1rdmania/ghostclaw/add-telegram-swarm)
Your own site
<a href="https://agentmods.dev/skills/b1rdmania/ghostclaw/add-telegram-swarm"><img src="https://agentmods.dev/badge/skills/b1rdmania/ghostclaw/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.

agentmods 80×15 button for add-telegram-swarm

Your own site · 80×15
<a href="https://agentmods.dev/skills/b1rdmania/ghostclaw/add-telegram-swarm"><img src="https://agentmods.dev/badge/skills/b1rdmania/ghostclaw/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,630 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 86% 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.00064 $0.03630
Opus 5 $0.00032 $0.01815
Sonnet 5 $0.00013 $0.00726
Haiku 4.5 $0.00006 $0.00363

Measured 10d ago against content hash ecaa4ebdf341, 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 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.

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

86% identical to add-telegram-swarm — 40 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 · 385 lines

How it starts

The opening of the file, as written. The whole thing — 385 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.

  1. Open Telegram and search for @BotFather
  2. 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.
  3. Copy all the tokens
  4. 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:

  1. Send /mybots and select the bot
  2. Go to Bot Settings > Group Privacy > Turn off

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

Read the full file on GitHub · 385 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 · 385 lines · 64 tokens per session scan A ecaa4ebdf341

Subscribe to this mod's changes

add-telegram-swarm is a skill published in the GitHub repository b1rdmania/ghostclaw (92 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 3,630 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 86% identical to add-telegram-swarm, differing in 40 lines, and is treated as a copy.

Related

Other skills, from other repositories

lobu-operator

Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.

lobu-ai/lobu · 0 tokens

company-agent-infrastructure

Use when designing or building internal/company AI agents that need shared context across company systems, durable organizational memory across sessions or agents, user-scoped permissions, approvals, audit, or governed actions. Also use when deciding whether ordinary MCP tools, RAG, or local agent memory are enough…

lobu-ai/lobu · 70 tokens

lobu-builder

Use when working inside a Lobu project generated by @lobu/cli or any repository centered on lobu.config.ts, AGENTS.md, agent prompt files, local skills, and evals. This skill helps a coding agent inspect the right files, make Lobu-native changes, keep the stack runnable, and validate semantics with chat tests and…

lobu-ai/lobu · 76 tokens

crm-ops

How to operate the Lobu funnel CRM — create and enrich leads, log interactions, advance funnel stages, open and update pilots, and produce the weekly digest. Use whenever the task touches the pipeline.

lobu-ai/lobu · 44 tokens

deliveroo-order

Turn collected lunch orders into a clean per-person order list for a human to place on Deliveroo. Use in step 2 of the lunch run, after orders are collected. The live menu is fetched automatically by the lobu-team-lunch-finalize reaction (via the Owletto Chrome extension) — this skill never places an order or touches…

lobu-ai/lobu · 75 tokens

lobu

Use Lobu MCP for shared, permission-aware company context, durable organizational memory, and governed actions. Trigger when the user asks what the organization knows, needs context from connected company systems, wants to preserve a durable fact or decision, or needs to discover and use Lobu SDK capabilities.

lobu-ai/lobu · 60 tokens