Borrowing it
Nothing to install: this file belongs to alexeyleshchenko/fast-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/alexeyleshchenko/fast-mcp-telegram/master/CLAUDE.mdgit clone --depth 1 https://github.com/alexeyleshchenko/fast-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/alexeyleshchenko/fast-mcp-telegram/claude-md)<a href="https://agentmods.dev/instructions/alexeyleshchenko/fast-mcp-telegram/claude-md"><img src="https://agentmods.dev/badge/instructions/alexeyleshchenko/fast-mcp-telegram/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/alexeyleshchenko/fast-mcp-telegram/claude-md"><img src="https://agentmods.dev/badge/instructions/alexeyleshchenko/fast-mcp-telegram/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.00882 | $0.00882 |
| Opus 5 | $0.00441 | $0.00441 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
fast-mcp-telegram CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Correct approach**: ACL is not viable through Cursor MCP (stdio has no ACL; URL MCP uses a fixed bearer; stale MCP subprocesses). Use `pytest tests/test_session_acl.py tests/test_mcp_tool_acl_integration.py`, HTTP cu This is a copy
100% identical to fast-mcp-telegram CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fast-mcp-telegram
Canonical GitHub repository: https://github.com/alexeyleshchenko/fast-mcp-telegram
Canonical Python package: fast-mcp-telegram on PyPI (https://pypi.org/project/fast-mcp-telegram/).
Canonical MCP registry name: io.github.alexeyleshchenko/fast-mcp-telegram
The old GitHub URL https://github.com/leshchenko1979/fast-mcp-telegram is a public 404. Do not restore that owner in README links, pyproject.toml, server.json, glama.json, GHCR image names, or docs clone URLs. PyPI is the stable pointer.
Do not create a replacement repository under leshchenko1979/fast-mcp-telegram. If GitHub ever unsuspends that account and allows a transfer, keep the old name free so redirects can work.
Telegram MCP server (stdio, http-no-auth, http-auth). Full setup, ACL matrix, and dev workflow: CONTRIBUTING.md.
Session Corrections
2026-05-27
- Issue: Tried ACL live testing via Cursor MCP (
telegram-devor http-auth URL with fixedAuthorization)- Correct approach: ACL is not viable through Cursor MCP (stdio has no ACL; URL MCP uses a fixed bearer; stale MCP subprocesses). Use
pytest tests/test_session_acl.py tests/test_mcp_tool_acl_integration.py, HTTP curl against a local http-auth server, andscripts/acl_mcp_smoke.sh(reads bearer tokens fromacl.dev.yaml, not hardcoded placeholders) — see CONTRIBUTING.md § ACL development and testing
- Correct approach: ACL is not viable through Cursor MCP (stdio has no ACL; URL MCP uses a fixed bearer; stale MCP subprocesses). Use
- Issue: Started http-auth ACL server from wrong cwd, or
source .env.localin zsh forMTPROTO_PROXY- Correct approach: Start the server from the project root so Python loads
.env/.env.localvia dotenv; do notsource .env.localin zsh — proxy URLs with&break shell parsing
- Correct approach: Start the server from the project root so Python loads
- Issue: Assumed ACL applies in stdio or without per-bearer sessions
- Correct approach: ACL enforces only with
SERVER_MODE=http-authandACL_ENABLED=true; each bearer inacl.dev.yamlneeds a matching{token}.sessionviahttp://127.0.0.1:8765/setup
- Correct approach: ACL enforces only with
- Issue: Expected
connection.pystdio fix without restarting Cursor MCP- Correct approach: After changing server code used by telegram-dev, restart telegram-dev in Cursor’s MCP panel — stale subprocess keeps old behavior
- Issue: Risk of committing real ACL bearer tokens
- Correct approach: Keep
acl.dev.yamlgitignored; never commit real bearer tokens (template only:acl.dev.yaml.example)
- Correct approach: Keep
- Issue: "Repeat the sourcery-pr-cycle" interpreted as running another full PR → Sourcery → fix loop
- Correct approach: User may mean publish/commit the skill to master, not re-execute the review cycle. Confirm intent when ambiguous.
- Issue: Treated phase closeout as blocked until all follow-up PRs merge, or assumed phase 1 code cannot land on master while follow-ups are open
- Correct approach: Phase 1 code can be on master while follow-up PRs (e.g. #56) remain open; closeout means merge all blocking follow-ups first, not every open PR.
- Issue: Posted Telegram release announcement before release CI finished
- Correct approach: After
gh release create, verify CI/checks are green on the release tag or master commit (gh run list,gh release view); do not post Telegram until release is published and CI is green unless the user explicitly overrides — see release-notes skill
- Correct approach: After
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 · 34 lines · 882 tokens per session scan A a8d9aa37aed3
fast-mcp-telegram CLAUDE.md is an instructions file published in the GitHub repository alexeyleshchenko/fast-mcp-telegram (2 stars, last pushed 20d ago), licensed MIT. It adds 882 tokens to every session, about $0.0044 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to fast-mcp-telegram CLAUDE.md, differing in 0 lines, and is treated as a copy.
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).
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.
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.