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/vendelieu/telegram-botWrote 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/vendelieu/telegram-bot/telegram-bot-general)<a href="https://agentmods.dev/rules/vendelieu/telegram-bot/telegram-bot-general"><img src="https://agentmods.dev/badge/rules/vendelieu/telegram-bot/telegram-bot-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/vendelieu/telegram-bot/telegram-bot-general"><img src="https://agentmods.dev/badge/rules/vendelieu/telegram-bot/telegram-bot-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.00257 | $0.00257 |
| Opus 5.5 | $0.00103 | $0.00103 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
telegram-bot-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.
What it actually says
Telegram Bot General Rules
Kotlin Conventions
- Follow Kotlin coding conventions
- Run
./gradlew prepareReleasebefore committing
Gradle Tasks
./gradlew prepareRelease- format, api validation, kdocs, api violations check, ktnip:jvmTest./gradlew apiDump- generate api dump./gradlew :ktnip:jvmTest- run KSP processor tests (included in prepareRelease)
Contributing
- Target branch for PRs: dev
- Add tests for new code
- Use
@TgAPIon Action classes and top-level API functions for validation
API Validation
- api-sentinel validates actions against Telegram API spec
- Required params must be non-null; optional params must be nullable
- Method names must match
@TgAPI.Nameannotation
Handling Architecture
For Activity, WizardActivity, functional DSL vs annotation approach, and ProcessingPipeline, see telegram-bot-handling.mdc.
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 · 34 lines · 257 tokens per session scan A a4a3d373e5e5
telegram-bot-general is a cursor rule published in the GitHub repository vendelieu/telegram-bot (249 stars, last pushed today), licensed Apache-2.0. It adds 257 tokens to every session, about $0.0010 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
kotlin-ktor-development-cursorrules-prompt-file
Cursor rules for Kotlin development with Ktor integration.
kotlin-springboot-best-practices-cursorrules-prompt-file
Cursor rules for Kotlin Springboot Best Practices.
backend-server
Cursor rule "backend-server" from groupultra/telegram-search, covering backend server (apps/server), bootstrap & lifecycle, http & websocket design, configuration & environment and error handling & observability.
core
Cursor rule "core" from groupultra/telegram-search, covering core (packages/core), events & corecontext, database & drizzle, message resolvers & pipelines and error handling & logging.
kotlin-springboot-rules
A set of coding rules for Kotlin applications built with Spring Boot, a Java-based framework for web services. It covers project layout, naming, Kotlin style, and common design patterns.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.