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/itechmeat/llm-code/telegramnpx skills add itechmeat/llm-code --skill telegramgit clone --depth 1 https://github.com/itechmeat/llm-codeWhat 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.00126 | $0.00878 |
| Opus 5 | $0.00063 | $0.00439 |
| Sonnet 5 | $0.00025 | $0.00176 |
| Haiku 4.5 | $0.00013 | $0.00088 |
Grade A, and why
telegram 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram (Skill Router)
Router skill: pick the reference that matches your task.
Quick Navigation
| Task | Reference |
|---|---|
| New to Telegram bots | bots-overview.md |
| Bot capabilities overview | bot-features.md |
| API methods/types | bot-api.md |
| Webhook setup & security | webhooks.md |
| aiogram 3 handlers/FSM | aiogram-patterns.md |
| Keyboard UX | keyboard-design.md |
| Inline mode | inline-mode.md |
| Mini Apps (Web Apps) | mini-apps.md |
| Payments (Stars) | payments.md |
| Authentication (Login Widget, URL Auth) | authentication.md |
| Rate limits & performance | performance.md |
Critical Prohibitions
- ❌ No polling + webhooks simultaneously for same bot
- ❌ No hardcoded tokens/secrets — use environment variables
- ❌ No secrets in callback_data or logs
- ❌ No ignoring
answer_callback_query— always respond - ❌ No blocking work in webhook handlers — use background tasks
- ❌ No trusting Login Widget data without hash verification
Definition of Done
- Webhook handlers validate
X-Telegram-Bot-Api-Secret-Token - Keyboards: max 2 buttons per row, mobile-first
- Callback data validated, not trusted blindly
- Handlers are idempotent or have de-duplication
What ships with it
11 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.
- references/aiogram-patterns.md 6.4 KB
- references/authentication.md 5.0 KB
- references/bot-api.md 9.2 KB
- references/bot-features.md 5.0 KB
- references/bots-overview.md 2.8 KB
- references/inline-mode.md 4.5 KB
- references/keyboard-design.md 1.7 KB
- references/mini-apps.md 3.9 KB
- references/payments.md 9.7 KB
- references/performance.md 1.1 KB
- references/webhooks.md 3.5 KB
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 · 65 lines · 126 tokens per session scan A 115429e6cff4
telegram is a skill published in the GitHub repository itechmeat/llm-code (22 stars, last pushed 1mo ago), licensed MIT. It adds 126 tokens to every session and 878 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…