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 skills add isvlasov/rageatc-oss --skill building-telegram-botsgit clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/building-telegram-bots)<a href="https://agentmods.dev/skills/isvlasov/rageatc-oss/building-telegram-bots"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/building-telegram-bots/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/skills/isvlasov/rageatc-oss/building-telegram-bots"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/building-telegram-bots.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.00068 | $0.01024 |
| Opus 5 | $0.00034 | $0.00512 |
| Sonnet 5 | $0.00014 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
building-telegram-bots 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 10d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Telegram Bots
Prevents stale-knowledge failures when writing Telegram bot code. The Bot API updates roughly quarterly and frameworks more often, so training-time knowledge is unreliable — this skill enforces a verification protocol (detect, fetch, confirm) before any bot code is generated.
Scope
Covered: python-telegram-bot, aiogram (Python); grammY, Telegraf (Node.js)
Not covered: Other languages or frameworks; Telegram client API (TDLib); bot deployment and hosting; payment and monetisation APIs
Verification Protocol
Run this protocol before writing any bot code. Do not skip steps.
Step 1 — Detect the project framework and version
Read the project dependency manifest:
- Python project: check
pyproject.tomlfirst, thenrequirements.txt - Node.js project: read
package.json→dependenciesanddevDependencies
Identify which framework is present and its pinned or constrained version. If a lock file exists (package-lock.json, poetry.lock, uv.lock), read it for the exact resolved version.
See references/framework-guide.md → "Detecting Framework Version from Project Files" for manifest patterns.
Step 2 — Identify the Bot API version the framework targets
Map the framework version to its supported Bot API version.
See references/framework-guide.md → "Framework Fact Sheets" for the current mapping table.
Staleness warning: If the project uses Telegraf v4.x, issue an explicit warning before proceeding. See references/framework-guide.md → "Telegraf Staleness Warning" for required warning text.
Step 3 — Fetch the current Bot API changelog
Fetch https://core.telegram.org/bots/api#recent-changes to identify the current Bot API version. Compare it to the version the project's framework targets. Note any gap.
If the user is asking about a feature introduced in a Bot API version newer than the framework's support ceiling, tell them the framework does not yet support it.
Step 4 — Fetch framework-specific documentation for the feature being built
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 84 lines · 68 tokens per session scan A 6f7072a27fd2
building-telegram-bots is a skill published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,024 once invoked, about $0.0003 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-31.
Other skills, from other repositories
php-ecosystem-reference
Use when picking a non-Laravel PHP tool — Symfony components, API Platform, or Slim — and routing to implementation. Do NOT use for Laravel (laravel-expert).
php-http-psr
Use when building framework-agnostic PHP HTTP code — PSR-7/15/17/18 messages, middleware, factories, clients. Do NOT use for Laravel HTTP or Symfony HttpFoundation (not PSR-7).
rust-web-backend
Use when building a REST/HTTP backend in Rust — axum routing, extractors, shared state, middleware, error responses, sqlx database access. Not for raw async/concurrency (rust-async-concurrency).
backend-development
Use when building or structuring a Python backend on FastAPI + SQLAlchemy 2.0 (async) + Alembic + Pydantic v2. Provides the opinionated project layout, the standard kit (auth, async jobs, caching, storage, observability), and best practices.
odoo-python
Use when writing or reviewing any Python in an Odoo module — models, computes, overrides, controllers, wizards. Carries PSAE review-derived principles for ORM correctness, performance, style, and security, plus references for exact patterns. Invoke before writing logic in models/, controllers/, or wizard/.
django-expert
Use when building Django web applications or REST APIs with Django REST Framework. Invoke when working with settings.py, models.py, manage.py, or any Django project file. Creates Django models with proper indexes, optimizes ORM queries using selectrelated/prefetchrelated, builds DRF serializers and viewsets, and…