agentmods.dev

connect-telegram

connect-telegram is a skill for Claude Code, Codex from matteblack9/coding-agent-fabric. It costs 30 tokens per session (720 once invoked), scanned C, original, MIT.

A setup workflow for connecting a Telegram bot, an account operated through Telegram's BotFather service, to an existing orchestrator.

In plain words
What is it for?
Use it to collect or rotate a BotFather token, configure an optional user allowlist, store the credentials, and validate long-polling startup.
Why use it?
It checks that the orchestrator is ready, preserves existing credentials unless replacement is confirmed, and lets you restrict which Telegram users can reach the bot.

Skill for Claude CodeCodex

not rated 2 5mo ago C scan 30 tokens original MIT
View the source file matteblack9/coding-agent-fabric
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.

agentmods
npx agentmods add skills/matteblack9/coding-agent-fabric/connect-telegram
Any agent
npx skills add matteblack9/coding-agent-fabric --skill connect-telegram
Clone the repo
git clone --depth 1 https://github.com/matteblack9/coding-agent-fabric

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.

agentmods badge for connect-telegram

README.md
[![agentmods](https://agentmods.dev/badge/skills/matteblack9/coding-agent-fabric/connect-telegram.svg)](https://agentmods.dev/skills/matteblack9/coding-agent-fabric/connect-telegram)
Your own site
<a href="https://agentmods.dev/skills/matteblack9/coding-agent-fabric/connect-telegram"><img src="https://agentmods.dev/badge/skills/matteblack9/coding-agent-fabric/connect-telegram.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 720 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.00720
Opus 5 $0.00015 $0.00360
Sonnet 5 $0.00006 $0.00144
Haiku 4.5 $0.00003 $0.00072

Measured 4d ago against content hash 9510922cfd25, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

connect-telegram scanned grade C 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 4d 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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

### 3. Collect Credentials
skills/connect-telegram/SKILL.md · 121 lines

How it starts

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

connect-telegram

When To Use

  • The user wants to connect Telegram to the orchestrator
  • Telegram credentials are missing or need rotation
  • channels.telegram.enabled must be enabled in orchestrator.yaml

Runtime Adaptation

  • claude Read this file first, then use CLAUDE.md or .claude/ only as extra repo context.
  • cursor Follow this file first, then apply .cursor/rules, AGENTS.md, and CLAUDE.md if they add repo-specific policy.
  • codex Treat this file as the main Telegram setup checklist.
  • opencode Follow this file first, then layer AGENTS.md and any OpenCode-only overrides on top.

Rules

  • Never overwrite existing Telegram credentials without confirmation
  • Present detected values as numbered choices where possible
  • Store credentials under ARCHIVE/telegram/credentials
  • Empty allowed_users means the bot accepts all reachable Telegram users

Procedure

1. Verify Orchestrator

Check that orchestrator.yaml exists. If not, stop and run the setup-orchestrator skill first.

Resolve ARCHIVE_PATH from orchestrator.yaml, then inspect whether ARCHIVE/telegram/credentials already exists.

2. Telegram Bot Guide

If the user does not already have a bot token, guide them through BotFather:

1. Open Telegram and search for @BotFather
2. Send /newbot
3. Choose a bot display name
4. Choose a bot username ending in `bot`
5. Copy the full token BotFather returns

3. Collect Credentials

Ask for:

bot_token
allowed_users (optional, comma-separated usernames or numeric user IDs)

Validation rules:

  • bot_token is required and must contain a colon
  • allowed_users is optional

Summary before writing:

Telegram credentials entered:
  bot_token:      123456:...
  allowed_users:  username1, username2

Save with these values? (yes/no)

4. Save And Configure

Write:

bot_token : 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11
allowed_users : username1, username2

to:

Read the full file on GitHub · 121 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. 4d ago First seen · 121 lines · 30 tokens per session scan C 9510922cfd25

Subscribe to this mod's changes

connect-telegram is a skill published in the GitHub repository matteblack9/coding-agent-fabric (2 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 720 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Backend and APIs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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