add-telegram-api-tests

add-telegram-api-tests is a skill for Claude Code, Codex, Cursor from vendelieu/telegram-bot. It costs 44 tokens per session (677 once invoked), scanned A, original, Apache-2.0.

A workflow for writing tests for Telegram Bot API actions in Kotlin using the Kotest testing framework. It defines the test base class, request helpers, response checks, rate-limit handling, and test location.

In plain words
What is it for?
Use it when adding a test for a new Telegram method or API action. It helps create suspend tests, send requests to chats, verify responses, check error messages, and place files correctly.
Why use it?
It keeps Telegram API tests consistent across the library and makes common success and failure cases explicit. It also accounts for Telegram's 429 rate-limit response.

Skill for Claude CodeCodexCursor

Install

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.

agentmods
npx agentmods add skills/vendelieu/telegram-bot/add-telegram-api-tests
Any agent
npx skills add vendelieu/telegram-bot --skill add-telegram-api-tests
Clone the repo
git clone --depth 1 https://github.com/vendelieu/telegram-bot

Made for: Claude Code, Codex, Cursor.

Wrote 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.

agentmods badge for add-telegram-api-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/vendelieu/telegram-bot/add-telegram-api-tests.svg)](https://agentmods.dev/skills/vendelieu/telegram-bot/add-telegram-api-tests)
Your own site
<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>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 677 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 5d ago against content hash 8a214b7c8fa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursor/skills/add-telegram-api-tests/SKILL.md · 72 lines

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) or action.sendReq(CHAT_ID)
  • SimpleAction: action.sendReq(via = bot) or action.sendReq()
  • MediaAction: same as Action
  • Defaults: sendReq() uses TG_ID and bot when omitted

3. Assertions

  • Success: .shouldSuccess() - asserts ok, isSuccess, getOrNull not null
  • Optional result: .getOrNull() when success not guaranteed
  • Failure: .shouldFailure() - returns Response.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 ID
  • BOT_TOKEN - bot token from BotFather

Optional:

  • CHAT_ID - for chat/group tests
  • CHANNEL_ID - for channel tests
  • BOT_TOKEN_2 - rate-limit testing

Reference Examples

Read the full file on GitHub · 72 lines

Changes

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.

  1. 5d ago First seen · 72 lines · 44 tokens per session scan A 8a214b7c8fa5

Subscribe to this mod's changes

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.