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 skills/vendelieu/telegram-bot/add-telegram-api-testsnpx skills add vendelieu/telegram-bot --skill add-telegram-api-testsgit 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/skills/vendelieu/telegram-bot/add-telegram-api-tests)<a href="https://agentmods.dev/skills/vendelieu/telegram-bot/add-telegram-api-tests"><img src="https://agentmods.dev/badge/skills/vendelieu/telegram-bot/add-telegram-api-tests.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.00677 |
| Opus 5 | $0.00022 | $0.00338 |
| Sonnet 5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
add-telegram-api-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Telegram API Tests
Workflow
1. Test Class Setup
- Extend BotTestContext (provides
bot,TG_ID,CHAT_ID,CHANNEL_ID) - Use Kotest AnnotationSpec with
@Test suspend fun - Test names: backtick string e.g.
`method name method test`
class MyApiTest : BotTestContext() {
@Test
suspend fun `my method test`() {
// ...
}
}
2. API Call Helpers
- Action (chat-based):
action.sendReq(to = TG_ID, via = bot)oraction.sendReq(CHAT_ID) - SimpleAction:
action.sendReq(via = bot)oraction.sendReq() - MediaAction: same as Action
- Defaults:
sendReq()usesTG_IDandbotwhen omitted
3. Assertions
- Success:
.shouldSuccess()- asserts ok, isSuccess, getOrNull not null - Optional result:
.getOrNull()when success not guaranteed - Failure:
.shouldFailure()- returnsResponse.Failure - Error text:
response.shouldFailure() shouldContainInDescription "ERROR_TEXT"
4. Rate Limits (429)
For methods that may hit rate limits (e.g. setMyName):
val result = setMyName("test").sendReq()
result.onFailure { if (it.errorCode == 429) return }
result.shouldSuccess()
5. Test Placement
- Path:
telegram-bot/src/jvmTest/kotlin/eu/vendeli/api/ - Mirror API package:
botactions/,media/,message/,chat/, etc. - Add to existing test class if one exists for that API area
6. Environment
Tests load from .env or system env. Required for most tests:
TELEGRAM_ID- your Telegram user IDBOT_TOKEN- bot token from BotFather
Optional:
CHAT_ID- for chat/group testsCHANNEL_ID- for channel testsBOT_TOKEN_2- rate-limit testing
Reference Examples
- Bot actions: SetMyActionsTest.kt
- User/chat: UserTest.kt
- Message actions: MessageActionsTest.kt
- Failure assertion: MessageActionsTest.kt -
shouldFailure() shouldContainInDescription
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.
- 5d ago First seen · 72 lines · 44 tokens per session scan A 8a214b7c8fa5
add-telegram-api-tests is a skill published in the GitHub repository vendelieu/telegram-bot (248 stars, last pushed 8d ago), licensed Apache-2.0. It adds 44 tokens to every session and 677 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
headless-bot
Nested swiss-knife reference for creating and operating a headless LingTai bot project without opening the TUI. Start from lingtai-tui spawn, then apply the relevant addon/MCP wiring, keep secrets in sidecar files, copy preset policy by referencing existing presets instead of copying preset JSON files, refresh or…
telegram
Multi-bot Telegram bridge — routes messages between Telegram and Claude tmux sessions.
telegram-search-cli
Operate the Telegram Search CLI through an authorized local profile. Use when an agent needs to discover Telegram chats, read bounded remote messages, explicitly synchronize history with user-approved Telegram Takeout, query/search/contextualize persisted messages, compute statistics, export deterministic JSONL, or…
c-telegram
Bidirectional Telegram bridge — talk to Claude from your phone. Built into OpenPaw.
telegram-bot
Telegram bot development - chatbots, notifications, AI assistants, and group automation.
configure
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks "how do I set this up" or "who can reach me," or wants to check channel status.