telegram

A Telegram connection for Claude Code, allowing messages to reach the coding agent through Telegram. It includes controls for pairing users and managing who is allowed access.

In plain words
What is it for?
Use it to connect Claude Code to Telegram, configure pairing, manage allowlists, and apply access policy through /telegram:access.
Why use it?
It provides a controlled messaging bridge instead of leaving access open to every Telegram user. Access rules can be managed through the included command.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add anthropics/claude-plugins-official
agentmods
npx agentmods add plugins/anthropics/claude-plugins-official/telegram
Clone the repo
git clone --depth 1 https://github.com/anthropics/claude-plugins-official

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

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 2d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • telegram — 100% identical, 0 lines differ
  • telegram — 100% identical, 2 lines differ
external_plugins/telegram/.claude-plugin/plugin.json · 12 lines

What it actually says

{
  "name": "telegram",
  "description": "Telegram channel for Claude Code \u2014 messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.",
  "version": "0.0.7",
  "keywords": [
    "telegram",
    "messaging",
    "channel",
    "mcp"
  ]
}
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. 2d ago First seen · 12 lines scan A 6df50f47d8f5

Subscribe to this mod's changes

telegram is a plugin published in the GitHub repository anthropics/claude-plugins-official (35,799 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.