Borrowing it
Nothing to install: this file belongs to antongsm/mcp-telegram. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/antongsm/mcp-telegram/main/CLAUDE.mdgit clone --depth 1 https://github.com/antongsm/mcp-telegramWrote 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/instructions/antongsm/mcp-telegram/claude-md)<a href="https://agentmods.dev/instructions/antongsm/mcp-telegram/claude-md"><img src="https://agentmods.dev/badge/instructions/antongsm/mcp-telegram/claude-md.svg" alt="Measured on agentmods" 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.00490 | $0.00490 |
| Opus 5 | $0.00245 | $0.00245 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
mcp-telegram CLAUDE.md 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.
What it actually says
MCP Telegram
Unified Telegram MCP server — MTProto + Bot API.
Architecture
MCP Server (tg mcp)
├── user_* tools → HTTP → Daemon (:19876) → Telegram MTProto
└── bot_* tools → HTTPS → api.telegram.org → Telegram Bot
When to Use Which Tool
user_* — MTProto (Personal Account)
Use for sending messages from the user's account to other people:
| Tool | Description |
|---|---|
user_send_message |
Send text from user's account |
user_send_file |
Send file/photo/voice |
user_get_messages |
Get chat history |
user_search_dialogs |
Search contacts/chats |
user_download_media |
Download media from message |
user_edit_message |
Edit a message |
user_delete_messages |
Delete messages |
user_check_daemon |
Check daemon status |
Examples:
Send @username a message "Hello!"
Send file /path/to/doc.pdf to @username
Find contact John
bot_* — Bot API (Bot)
Use for Claude ↔ User communication:
| Tool | Description |
|---|---|
bot_send_message |
Send message via bot |
bot_send_file |
Send file via bot |
bot_send_photo |
Send photo via bot |
bot_send_voice |
Send voice message via bot |
bot_get_messages |
Get incoming messages |
bot_download_file |
Download file by file_id |
Examples:
Send me a Telegram message "Done!"
Check if there are new messages from the user
Important
-
Daemon must be running for user_* tools:
tg daemon start -
Configuration is stored in
~/.mcp-telegram/config.json -
On
Daemon not runningerror — start daemon or check status:tg daemon status
CLI Commands
tg login # Setup wizard
tg daemon start # Start daemon
tg daemon status # Check status
tg user send @user "text" # Send from user account
tg bot send "text" # Send via bot
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.
- 7d ago First seen · 79 lines · 490 tokens per session scan A 075e49aebf8d
mcp-telegram CLAUDE.md is an instructions file published in the GitHub repository antongsm/mcp-telegram (2 stars, last pushed 6mo ago), licensed MIT. It adds 490 tokens to every session, about $0.0024 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.