What is setup-telegram?

A guided setup skill for connecting a Telegram bot to a wolt. Telegram is a messaging service; the bot uses built-in platform code and needs configuration rather than new code.

Use it to create or find the bot's identity, configure the connection, and validate the setup.

It removes the need to work out the bot setup and identity steps manually, and can safely check an existing setup before changing it.

setup-telegram — Skill for Claude Code by jerpint/woltspace

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 jerpint/woltspace --skill setup-telegram

Clone the repo

git clone --depth 1 https://github.com/jerpint/woltspace

Made for: Claude Code.

Or install woltspace, the plugin that ships this one along with the rest of its 23 skills.

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/jerpint/woltspace/setup-telegram/github.svg)](https://agentmods.dev/skills/jerpint/woltspace/setup-telegram)

Your own site

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

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

When invoked 1,999 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.00018	$0.01999
Opus 5.5	$0.00007	$0.00800
Sonnet 5.5	$0.00004	$0.00400
Haiku 4.5	$0.00002	$0.00200

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

Security

Grade A, and why

setup-telegram 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 16d 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/setup-telegram/SKILL.md · 183 lines

How it starts

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

Telegram Setup

The owner does two things: pastes a BotFather token, then sends their bot any message. You write the configuration and verify the connection. Text messages use the wolts' existing harness setup; no dog or separate model API key is required. Voice notes need a transcription service: OpenAI by default (OPENAI_API_KEY), or any OpenAI-style one, a local server included (woltspace transcription set).

This skill is idempotent. Preserve unrelated configuration, existing allowed users, and working connections. Never print tokens or put them in shell arguments, logs, or summaries. Use the installed runtime and private configuration files.

1. Inspect and get the token

Find the active lodge's data root and configuration path: normally <wolts_dir>/.space/platform/config.json, or the explicit WOLTSPACE_CONFIG. Check woltspace status and existing channels.telegram settings without printing secrets. Environment values and the data root's .env can override configuration; check for conflicts before changing anything.

If Telegram is already configured and healthy, preserve its token and owner allowlist. Do not call getUpdates against a running connector. Report that it is connected; no new setup or restart is needed.

If a token exists, validate it using Telegram getMe without exposing its URL or token in output. Otherwise tell the owner:

Open Telegram and message @BotFather. Send /newbot and choose a name and username. Paste the token BotFather gives you here.

Store the token privately in channels.telegram.token, with enabled: false until the owner allowlist is ready. Merge fields rather than replacing the configuration; keep its permissions private (0600). Resolve conflicting legacy TELEGRAM_BOT_TOKEN / ENABLE_TELEGRAM_BOT settings in the same lodge config sources so the intended token and enablement take effect.

2. Learn the owner's user ID from their first message

Skip discovery when an existing nonempty allowed_users or TELEGRAM_ALLOWED_USERS is configured. Never replace an existing allowlist with an arbitrary sender.

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

16d ago Changed · +3 lines ff881583162f
26d ago Changed · -4 lines 0e1719a58d78
28d ago Changed · +3 lines fa23dacd8357
1mo ago Changed · +51 lines · -5 tokens per session be4cc8afc105
1mo ago Changed 027409d978d1
2mo ago First seen · 130 lines · 23 tokens per session scan A 59b8c1213a47

Subscribe to this mod's changes

setup-telegram is a skill published in the GitHub repository jerpint/woltspace (22 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,999 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-09-09.

Backend and APIs

setup-telegram next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
setup-telegramjerpint/woltspace	Skill	22	today	MIT	A	18	Claude Code
mem0-oss-to-platformmem0ai/mem0	Skill	69k	3d ago	Apache-2.0	A	217	Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	today	MIT	A	78	Claude Code
fastapi-router-pymicrosoft/skills	Skill	3.2k	today	MIT	A	46	Claude Code
dev-runtimelangwatch/langwatch	Skill	5.0k	today	Apache-2.0	A	172	Claude Code
api-designericrisco/rsc-harness	Skill	573	today	MIT	A	105	Claude Code, Codex
migrate-segw-to-raparc-mcp/arc-1	Skill	254	today	MIT	A	106	Claude Code