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.
/plugin marketplace add siriphonNott/claude-telegram-notify/plugin install telegram-notifyWrote 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.
[](https://agentmods.dev/skills/siriphonnott/claude-telegram-notify/telegram-notify)<a href="https://agentmods.dev/skills/siriphonnott/claude-telegram-notify/telegram-notify"><img src="https://agentmods.dev/badge/skills/siriphonnott/claude-telegram-notify/telegram-notify/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.
<a href="https://agentmods.dev/skills/siriphonnott/claude-telegram-notify/telegram-notify"><img src="https://agentmods.dev/badge/skills/siriphonnott/claude-telegram-notify/telegram-notify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00726 |
| Opus 5 | $0.00024 | $0.00363 |
| Sonnet 5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade C, and why
telegram-notify scanned grade C with 2 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
## Config (`~/.claude/telegram-notify/config.json`, chmod 600) Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `cat ~/.claude/telegram-notify/notify.log` How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram task-completion notifier
Sends a notification to a Telegram chat every time Claude Code finishes a turn
(1 turn = 1 message), via the plugin's UserPromptSubmit + Stop hooks. No
manual trigger needed once configured.
Per-user config/state/log live in ~/.claude/telegram-notify/ (override with
TELEGRAM_NOTIFY_HOME). The script is at ${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py.
First-time setup (guided)
The user needs a Telegram bot token (from @BotFather) and a chat id (the group/channel/DM the bot will post to; the bot must be a member).
- Ask the user for the bot token and chat id (one question at a time if needed).
- Write the config and send a live test:
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py" init \
--token "<BOT_TOKEN>" --chat-id "<CHAT_ID>" --language en
- Confirm the user received the test message. If not, run
statusand read the log.
To get a chat id: add the bot to the group, send a message, then open
https://api.telegram.org/bot<TOKEN>/getUpdates and read result[].message.chat.id.
Manage
# send a sample message now
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py" test
# preview without sending
TELEGRAM_NOTIFY_DRYRUN=1 python3 "${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py" test
# turn on / off
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py" enable
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py" disable
# show current config (token masked) + last log lines
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/telegram_notify.py" status
Config (~/.claude/telegram-notify/config.json, chmod 600)
| key | meaning |
|---|---|
bot_token |
Telegram bot token |
chat_id |
target chat id |
enabled |
master on/off (default true) |
language |
en (default) or th |
timezone |
IANA tz name, or null = system local |
skip_prompt_prefixes |
prompts starting with these tags are ignored (system/tool-injected turns) |
Secrets can also come from env TELEGRAM_BOT_TOKEN / TELEGRAM_CHAT_ID (override config).
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.
- 9d ago First seen · 67 lines · 49 tokens per session scan C b6874895ff39
telegram-notify is a skill published in the GitHub repository siriphonNott/claude-telegram-notify (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 726 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…