nano---Openclaw: Skill for Claude Code

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

add-telegram is a skill for Claude Code from ShinyStar307/nano---Openclaw. It costs 41 tokens per session (1,745 once invoked), scanned A, a copy of add-telegram, MIT.

A Telegram channel for sending messages to and receiving messages from NanoClaw through a Telegram bot.

In plain words
What is it for?
Use it to add Telegram messaging, replace WhatsApp, run both channels, or configure a Telegram bot for actions and notifications.
Why use it?
It lets users communicate with the agent in Telegram instead of WhatsApp, or use both channels. Telegram can be used for control commands only or for notifications only.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; names the AskUserQuestion tool.

This is ShinyStar307/nano---Openclaw's own configuration. It tells Claude Code how to work on nano---Openclaw 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 nano---Openclaw configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ShinyStar307/nano---Openclaw. 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/ShinyStar307/nano---Openclaw/main/.claude/skills/add-telegram/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ShinyStar307/nano---Openclaw

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

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

agentmods 80×15 button for add-telegram

Your own site · 80×15
<a href="https://agentmods.dev/skills/shinystar307/nano---openclaw/add-telegram"><img src="https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/add-telegram.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,745 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 92% 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.00041 $0.01745
Opus 5 $0.00020 $0.00873
Sonnet 5 $0.00008 $0.00349
Haiku 4.5 $0.00004 $0.00175

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

Security

Grade A, and why

add-telegram 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 8d 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.

- Verify token: `curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getMe"`
Origin

This is a copy

92% identical to add-telegram — 26 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/SKILL.md · 223 lines

How it starts

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

Add Telegram Channel

This skill adds Telegram support to NanoClaw, then walks through interactive setup.

Phase 1: Pre-flight

Check if already applied

Check if src/channels/telegram.ts exists. If it does, skip to Phase 3 (Setup). The code changes are already in place.

Ask the user

Use AskUserQuestion to collect configuration:

AskUserQuestion: Do you have a Telegram bot token, or do you need to create one?

If they have one, collect it now. If not, we'll create one in Phase 3.

Phase 2: Apply Code Changes

Ensure channel remote

git remote -v

If telegram is missing, add it:

git remote add telegram https://github.com/qwibitai/nanoclaw-telegram.git

Merge the skill branch

git fetch telegram main
git merge telegram/main || {
  git checkout --theirs package-lock.json
  git add package-lock.json
  git merge --continue
}

This merges in:

  • src/channels/telegram.ts (TelegramChannel class with self-registration via registerChannel)
  • src/channels/telegram.test.ts (unit tests with grammy mock)
  • import './telegram.js' appended to the channel barrel file src/channels/index.ts
  • grammy npm dependency in package.json
  • TELEGRAM_BOT_TOKEN in .env.example

If the merge reports conflicts, resolve them by reading the conflicted files and understanding the intent of both sides.

Validate code changes

npm install
npm run build
npx vitest run src/channels/telegram.test.ts

All tests must pass (including the new Telegram tests) and build must be clean before proceeding.

Phase 3: Setup

Create Telegram Bot (if needed)

If the user doesn't have a bot token, tell them:

I need you to create a Telegram bot:

  1. Open Telegram and search for @BotFather
  2. Send /newbot and follow prompts:
    • Bot name: Something friendly (e.g., "Andy Assistant")
    • Bot username: Must end with "bot" (e.g., "andy_ai_bot")
  3. Copy the bot token (looks like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11)

Read the full file on GitHub · 223 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. 8d ago First seen · 223 lines · 41 tokens per session scan A 1b84b326f176

Subscribe to this mod's changes

add-telegram is a skill published in the GitHub repository ShinyStar307/nano---Openclaw (5 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,745 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to add-telegram, differing in 26 lines, and is treated as a copy.