telegram-notify

telegram-notify is a command for Claude Code from siriphonNott/claude-telegram-notify. It costs 20 tokens per session (182 once invoked), scanned A, original, MIT.

A command for sending notifications to Telegram, a messaging app, when coding tasks finish.

In plain words
What is it for?
Use it to set up a Telegram bot and chat, send a test message, turn notifications on or off, and view their status.
Why use it?
It lets you know when work is complete without watching the agent or terminal. It also provides commands to check, enable, disable, test, or configure notifications.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the telegram-notify plugin — 1 skill, 1 command, 2 hooks shipped together

Good fit Use it to set up a Telegram bot and chat, send a test message, turn notifications on or off, and view their status.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add siriphonNott/claude-telegram-notify
Claude Code
/plugin install telegram-notify

Made for: Claude Code.

Or install telegram-notify, the plugin that ships this one along with the rest of its 1 skill, 1 command, 2 hooks.

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-notify

README.md
[![agentmods](https://agentmods.dev/badge/commands/siriphonnott/claude-telegram-notify/telegram-notify.svg)](https://agentmods.dev/commands/siriphonnott/claude-telegram-notify/telegram-notify)
Your own site
<a href="https://agentmods.dev/commands/siriphonnott/claude-telegram-notify/telegram-notify"><img src="https://agentmods.dev/badge/commands/siriphonnott/claude-telegram-notify/telegram-notify.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 182 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.00020 $0.00182
Opus 5 $0.00010 $0.00091
Sonnet 5 $0.00004 $0.00036
Haiku 4.5 $0.00002 $0.00018

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

Security

Grade A, and why

telegram-notify 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 7d 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.

commands/telegram-notify.md · 14 lines

What it actually says

The user ran /telegram-notify $ARGUMENTS. Map the first word of $ARGUMENTS to an action. Script path: ${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py.

  • setup (or empty): run the guided setup from the telegram-notify skill — ask for the bot token and chat id, then run init --token <…> --chat-id <…> and confirm the test message arrived.
  • test: run python3 "${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py" test.
  • on: run ... enable.
  • off: run ... disable.
  • status: run ... status and show the output.

If the action is unrecognized, show this list.

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. 7d ago First seen · 14 lines · 20 tokens per session scan A 7e301d640414

Subscribe to this mod's changes

telegram-notify is a command published in the GitHub repository siriphonNott/claude-telegram-notify (2 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 182 once invoked, about $0.0001 per session on Opus 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.