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.
npx agentmods add rules/vendelieu/telegram-bot/telegram-bot-testsgit clone --depth 1 https://github.com/vendelieu/telegram-botWhat 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 | $0.00000 | $0.00369 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
telegram-bot-tests 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 2d 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 Test Rules
Test Base
- Extend BotTestContext (provides
bot,TG_ID,CHAT_ID,CHANNEL_ID) - Use Kotest AnnotationSpec with
@Testfor suspend tests
class MyApiTest : BotTestContext() {
@Test
suspend fun `descriptive test name`() {
// ...
}
}
API Call Helpers
- Action:
action.sendReq(to = TG_ID, via = bot)oraction.sendReq(CHAT_ID) - SimpleAction:
action.sendReq(via = bot)oraction.sendReq() - MediaAction: same as Action
sendReq()returnsResponse<T>; usesendReturning()when you needDeferred
Assertions
- Success:
.shouldSuccess()- asserts ok, isSuccess, getOrNull not null - Failure:
.shouldFailure()- returnsResponse.Failure - Optional result:
.getOrNull()when success is not guaranteed - Error text:
response.shouldFailure() shouldContainInDescription "ERROR_TEXT"
Rate Limits
Handle 429 with onFailure:
val result = setMyName("test").sendReq()
result.onFailure { if (it.errorCode == 429) return }
result.shouldSuccess()
Environment
Tests load from .env or system env: TELEGRAM_ID, BOT_TOKEN, CHAT_ID, CHANNEL_ID, BOT_TOKEN_2, PAYMENT_PROVIDER_TOKEN
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.
- 2d ago First seen · 50 lines · 369 tokens per session scan A 543aab4ffe1c
telegram-bot-tests is a cursor rule published in the GitHub repository vendelieu/telegram-bot (248 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 369 tokens. 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
architecture
这是一个把 Telegram 消息导入、导出到数据库中并提供搜索的服务。支持向量搜索和语义匹配，基于 OpenAI 的语义向量技术。.
events
When adding a new event, ensure all of the following are updated in one change.
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.
client
Cursor rule "client" from groupultra/telegram-search, covering client adapters (packages/client), core runtime & bridge, events & type safety, pinia stores & composables and logging & error handling.
core
Cursor rule "core" from groupultra/telegram-search, covering core (packages/core), events & corecontext, database & drizzle, message resolvers & pipelines and error handling & logging.
frontend-web
Cursor rule "frontend-web" from groupultra/telegram-search, covering frontend (apps/web), routing, layouts & navigation, state & data fetching, ui, styling & ux and error handling & notifications.