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/leshchenko1979/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/rules/leshchenko1979/fast-mcp-telegram/general)<a href="https://agentmods.dev/rules/leshchenko1979/fast-mcp-telegram/general"><img src="https://agentmods.dev/badge/rules/leshchenko1979/fast-mcp-telegram/general/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/rules/leshchenko1979/fast-mcp-telegram/general"><img src="https://agentmods.dev/badge/rules/leshchenko1979/fast-mcp-telegram/general.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.00228 | $0.00228 |
| Opus 5.5 | $0.00091 | $0.00091 |
| Sonnet 5.5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
general 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- general — 100% identical, 0 lines differ
What it actually says
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
All comments, docstrings, and documentation must be in English only. Do not use any other non-English language in code comments, docstrings, or documentation.
Always use the DRY principle.
Always check today's date with shell command date when inserting current date.
Testing with telegram-dev MCP
This project has a telegram-dev MCP server configured in .cursor/mcp.json.
When you modify code, ask the user to restart the server in Cursor's MCP panel.
See CONTRIBUTING.md for setup instructions.
Releases
For release, version bump, tag, gh release, or publish requests, read and follow .cursor/skills/release-notes/SKILL.md in full before changing versions or publishing.
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 · 24 lines · 228 tokens per session scan A 044c543388bc
general is a cursor rule published in the GitHub repository leshchenko1979/fast-mcp-telegram (50 stars, last pushed 8d ago), licensed MIT. It adds 228 tokens to every session, about $0.0009 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-30.
Other cursor rules, from other repositories
example
You are in a workspace with Bifrost MCP tools enabled. Use them for code navigation, understanding, and modification. Follow these guidelines.
mcp
Rules written in Chinese for choosing an enhancement service based on the user's request. They cover feature changes, bug analysis, and project or architecture analysis.
bootstrap-alwayson
Minimal always-required LLM fixes.
monitoring
Monitoring, observability, and alerting rules.
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
single-commit-pr
Pull requests have exactly one commit: squash before opening, amend and force-push after.