telegram-operations

telegram-operations is a skill for Claude Code, Codex from CodeInfinity1/Stram. It costs 27 tokens per session (992 once invoked), scanned A, original, MIT.

A workflow for setting up and operating Telegram bots in private chats, groups, and discussion topics, including image-media conversion and approval-controlled sending.

In plain words
What is it for?
Use it to configure Telegram bot credentials and chat access, prepare messages and media, monitor incoming messages, and send approved messages.
Why use it?
It organizes setup checks, message preparation, listener checks, and sending steps so bot operations can be tested and controlled.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to configure Telegram bot credentials and chat access, prepare messages and media, monitor incoming messages, and send approved messages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/codeinfinity1/stram/telegram-operations
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 CodeInfinity1/Stram --skill telegram-operations
Clone the repo
git clone --depth 1 https://github.com/CodeInfinity1/Stram

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 telegram-operations

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/codeinfinity1/stram/telegram-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/telegram-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 992 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00992
Opus 5.5 $0.00011 $0.00397
Sonnet 5.5 $0.00005 $0.00198
Haiku 4.5 $0.00003 $0.00099

Measured 1mo ago against content hash 11090d0812c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

telegram-operations 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 1mo 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.

skills/communications/telegram-operations/SKILL.md · 103 lines

How it starts

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

Telegram Operations

Tool Map

  • channel_manifest
  • channel_setup_requirements
  • channel_setup_save
  • channel_setup_status
  • channel_doctor
  • channel_listener_status
  • channel_listener_tick
  • channel_webhook_ingest
  • channel_message_prepare
  • channel_action_prepare
  • channel_message_send
  • channel_outbox

Use this skill when Telegram bot setup, Telegram groups, topics, media conversion, or Telegram sends are involved.

Setup

  1. Create a bot with BotFather.
  2. Set TELEGRAM_BOT_TOKEN.
  3. Use numeric chat IDs as conversation_id.
  4. For supergroups, IDs usually start with -100.
  5. Save non-secret setup refs with channel_setup_save.
  6. Run channel_doctor for telegram.

Workflow

  1. Use channel_setup_requirements for Telegram's bot token, numeric chat ID rules, media conversion flag, and listener mode.
  2. Save enabled state, default chat ID, allowlists, group allowlists, and secret references with channel_setup_save.
  3. Run channel_setup_status, channel_doctor, and channel_listener_status.
  4. Use channel_integration_smoke for prepared envelope and dry-run send readiness.
  5. Use channel_listener_tick for Telegram long-polling smoke when TELEGRAM_BOT_TOKEN is configured.
  6. Use channel_webhook_ingest for webhook payload smoke when testing a posted update.
  7. Use channel_message_prepare and channel_action_prepare before any visible message, media send, reaction, topic reply, typing indicator, or read receipt.

Group Rules

For groups:

  • Put group chat IDs in group allowlists.
  • Put human sender IDs in sender allowlists.
  • Do not confuse negative group IDs with user IDs.
  • Require mentions by default.
  • Disable BotFather privacy mode or make the bot admin only when ambient group messages should be visible.

Topics

Represent topic-scoped conversations with structured metadata or a conversation id convention supplied by the runtime. Keep topic and base group context isolated.

Markdown Images

Telegram supports outbound media. Stram mechanically extracts markdown image syntax from prepared messages when the channel manifest says markdown_image_to_media:true.

Read the full file on GitHub · 103 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. 1mo ago First seen · 103 lines · 27 tokens per session scan A 11090d0812c2

Subscribe to this mod's changes

telegram-operations is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 992 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-08-31.

Related

Other skills, from other repositories

android-pentest

A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.

Netw0rkNoob/VulnClaw · 32 tokens

lighting-report-extract

Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.

AlpacaLabsLLC/skills-for-architects · 37 tokens

authentication-patterns

OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.

travisjneuman/.claude · 28 tokens

container-debugging

Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.

WrongStack/WrongStack · 45 tokens

alive:system-upgrade

Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.

alivecontext/alive · 57 tokens

pr-review

Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…

nitinjain999/platform-skills · 81 tokens