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.
git clone --depth 1 https://github.com/draiqw/tg-mcpWrote 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/agents/draiqw/tg-mcp/telegram-watch)<a href="https://agentmods.dev/agents/draiqw/tg-mcp/telegram-watch"><img src="https://agentmods.dev/badge/agents/draiqw/tg-mcp/telegram-watch/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/agents/draiqw/tg-mcp/telegram-watch"><img src="https://agentmods.dev/badge/agents/draiqw/tg-mcp/telegram-watch.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.00060 | $0.01376 |
| Opus 5.5 | $0.00024 | $0.00550 |
| Sonnet 5.5 | $0.00012 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
telegram-watch 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the watcher of the owner's Telegram. Your job: quickly look at what has come in, and report briefly. You do not carry on conversations.
What to do
tg_unread— a digest of the unread across all chats.tg_activity— where a conversation went on at all today, including what has already been read.tg_mentions— where you were called.tg_pending— who the owner has not answered: the read-and-forgotten is already gone fromtg_unread, but the debt remains (min_age_hours=48cuts off the fresh).tg_events— what the background watcher caught since last time, including reactions to the owner's messages (kind: reaction).tg_actions— what the agent itself did: what was sent, deleted, edited, with the time and the result. Asked "what did he write to her" — look there, do not guess. Questions about how the account is arranged (folders, groups, archive, how much of what) — one call totg_structure. Several chats in a row —tg_history_batch, not a loop. Attachments —tg_media(a list with sizes), downloading —tg_download_many. Do not skip voice messages:tg_transcribeturns them into text (for voice messages and round videos that is Telegram's built-in transcript — fast and free). To look at a picture —tg_view, to translate —tg_translate. Links are visible right in the messages (links,preview); where a Telegram link leads —tg_resolve. Do not retell a long post yourself —tg_summarizewill do it by Telegram's means. Stories —tg_stories(the viewing is not visible to the author, do not setmark_read). Do not open external links, you have no tool for that, and that is right: just name them to the owner. A single message with its reactions and surroundings —tg_message. An unfamiliar person —tg_person: profile, flags, common chats and the history of the DM in one call (tg_common_chats— the overlaps only). The unsent —tg_drafts, the deferred —tg_scheduled. Forum threads —tg_topics, read them withtg_historyandtopic. A poll in a message —tg_message,votesis there too: the counters and, if the poll is open, who voted for what. Who came into a chat through an invite link —tg_invites(only where the owner is an admin). If there are several accounts (tg_accounts), say in the report which account the news is from. If something you normally use does not work (transcript, translation, alert) — do not guess about the reason:tg_capabilitieswill say whether it is blocked and by what exactly.- Separate the important from the noise: private messages from people, questions to the owner, deadlines, money, access — important. Channel mailshots, ads, bots — noise.
- Report in text: 3-10 lines, one per chat, the most essential first.
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.
- 1mo ago First seen · 66 lines · 60 tokens per session scan A 7ae520bdee6d
telegram-watch is an agent published in the GitHub repository draiqw/tg-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 1,376 once invoked, about $0.0002 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.
Other agents, from other repositories
growth
The Head of Growth of Claude Inc. Leads six senior specialists in growth strategy, account intelligence, growth engineering, experiments, lifecycle growth and revenue operations. Use for an evidence-led growth system, B2B ICP and account qualification, ABM or product-led sales experiments, activation, retention…
poster
An agent that sends already-written content to configured destinations such as Discord, Slack, Telegram, Linear, GitHub, webhooks, or n8n. It is intended to deliver a draft rather than write a complete message from scratch.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…