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-tests)<a href="https://agentmods.dev/rules/vendelieu/telegram-bot/telegram-bot-tests"><img src="https://agentmods.dev/badge/rules/vendelieu/telegram-bot/telegram-bot-tests/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-tests"><img src="https://agentmods.dev/badge/rules/vendelieu/telegram-bot/telegram-bot-tests.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.00369 | $0.00369 |
| Opus 5.5 | $0.00148 | $0.00148 |
| Sonnet 5.5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $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 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 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.
- 1mo 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 (249 stars, last pushed 3d ago), licensed Apache-2.0. It adds 369 tokens to every session, about $0.0015 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
architectural-planning
Architectural planning guidelines for Level 4 Complex System tasks.
archive-comprehensive
Comprehensive archiving approach for Level 4 Complex System tasks.
phased-implementation
Phased Implementation for Level 4 Complex System tasks.
reflection-comprehensive
Comprehensive reflection format for Level 4 Complex System tasks.
qa-mode-map
Cursor rule "qa-mode-map" from bia-technologies/yaxunit, covering 🔍 enhanced qa mode process flow, 🧭 phase detection process, 📝 universal memory bank verification, 📋 task tracking verification and 🔄 reference validation process.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.