Borrowing it
Nothing to install: this file belongs to n24q02m/better-telegram-mcp. 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/n24q02m/better-telegram-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/n24q02m/better-telegram-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/instructions/n24q02m/better-telegram-mcp/claude-md)<a href="https://agentmods.dev/instructions/n24q02m/better-telegram-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/n24q02m/better-telegram-mcp/claude-md/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/instructions/n24q02m/better-telegram-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/n24q02m/better-telegram-mcp/claude-md.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.01932 | $0.01932 |
| Opus 5 | $0.00966 | $0.00966 |
| Sonnet 5 | $0.00386 | $0.00386 |
| Haiku 4.5 | $0.00193 | $0.00193 |
Grade A, and why
better-telegram-mcp 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 10d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - better-telegram-mcp
MCP Server cho Telegram. Python 3.13, uv, hatchling, src layout. Dual-mode: Bot API (httpx) + MTProto (Telethon). 7 tools: message, chat, media, contact, config, help, config__open_relay.
Commands
uv sync --group dev # Setup
uv run ruff check . # Lint
uv run ruff format --check . # Format check
uv run ty check # Type check
uv run pytest # Test (integration excluded)
uv run ruff check --fix . && uv run ruff format . # Fix
Cau truc
src/better_telegram_mcp/
config.py # Pydantic Settings, env prefix TELEGRAM_
server.py # FastMCP + lifespan + auth mode switching
credential_state.py # save_credentials/on_step_submitted callbacks +
# _current_sub contextvar (multi-user routing)
auth/
telegram_auth_provider.py # Per-sub Telethon backend lifecycle
in_memory_session_store.py # bearer/sub -> SessionInfo (RAM only)
backends/ # TelegramBackend ABC -> BotBackend (httpx), UserBackend (Telethon)
backends/security.py # validate_url, validate_file_path, validate_output_dir
relay_setup.py # Shared error sanitization, field constants
relay_schema.py # Relay schema + TELEGRAM_TABS layout + render_telegram_form
# (Bot/User tabs drawn by mcp-core render_credential_form)
transports/
http.py # _start_single_user_http + _start_multi_user_http
# (both via mcp-core run_http_server)
credential_store.py# Master-secret resolution helper
tools/ # messages, chats, media, contacts, config_tool, help
Auth flow
Stdio mode (default): local single-user mode. Bot mode uses
TELEGRAM_BOT_TOKEN; user mode can be configured with the local auth CLI
(login is a deprecated alias).
HTTP mode (--http / MCP_TRANSPORT=http): mcp-core run_http_server
serves the local OAuth AS at /authorize. The custom credential form
collects bot_token OR phone, posts to /save, and chains OTP / 2FA via
/otp.
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.
- 10d ago First seen · 144 lines · 1,932 tokens per session scan A c19943e822cf
better-telegram-mcp CLAUDE.md is an instructions file published in the GitHub repository n24q02m/better-telegram-mcp (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,932 tokens to every session, about $0.0097 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-30.
Other instructions, from other repositories
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.