telegram-userbots SKILL.md skillA
telegram-userbots from ssheleg/telegram-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ssheleg/telegram-dev/telegram-userbots@git:20261025.d064a93Pins git:20261025.d064a93 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ssheleg/telegram-dev
- Path
plugins/telegram-dev/skills/telegram-userbots/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261025.d064a93, committed Oct 25, 2026
- First version recorded
- Aug 25, 2026
- Size
- 9,051 bytes
- Repository stars
- 4
- License
- MIT
Use when a Telegram job needs a user account, not a bot token: history a bot cannot see, acting as a person, bulk export over MTProto, and the ban risk. Not for bots (telegram-bots) or Mini Apps (telegram-miniapps). Opt out: no telegram, без телеграма. Triggers - "telethon", "userbot", "юзербот".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Telegram userbots — MTProto, and what it costs A bot token is issued to software. **An MTProto session is a logged-in human being** — the same authority the person has, held in a file, with none of the protections a token has. Everything in this skill follows from that one difference. *Read against Telethon **1.44.0** and `core.telegram.org` on 2026-08-25. Telethon minor releases change session and entity-cache behaviour; the version you are on is a fact to check, not to assume.* Deep material, loaded on demand: | Read | When | |---|---| | [`references/sessions-and-auth.md`](references/sessions-and-auth.md) | logging in, storing a session, rotating one, or moving between machines | | [`references/rate-and-flood.md`](references/rate-and-flood.md) | anything that loops over chats, users or messages — FloodWait, pacing, takeout | | [`references/entities-and-history.md`](references/entities-and-history.md) | resolving peers, iterating history, downloading media at scale | --- ## First: do you actually need one? Answer this before writing a line, and write the answer down. | The job | Bot API can | Verdict | |---|---|---| …
Read the whole file at its exact version.
How to install
mdr add ssheleg/telegram-dev/telegram-userbots@sha256:c08e0487fd98d1b8The line at the top of this page pins the label git:20261025.d064a93, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yzcmwrajwjxkrq2a)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 25, 2026 and Oct 25, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.d064a93 latest | 2026-10-25 | d064a93 | 9,051 B | A | view · diff |
| git:20261020.94251ea | 2026-10-20 | 94251ea | 9,115 B | A | view · diff |
| git:20261019.dfa267c | 2026-10-19 | dfa267c | 9,446 B | A | view · diff |
| git:20260909.3ac31db | 2026-09-09 | 3ac31db | 8,652 B | A | view · diff |
| git:20260825.74bbb9a | 2026-08-25 | 74bbb9a | 7,967 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9051 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ssheleg/telegram-dev · 4 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yzcmwrajwjxkrq2a GET https://markdownregistry.com/api/v1/resolve?ref=ssheleg/telegram-dev/telegram-userbots GET https://markdownregistry.com/api/v1/blob/c08e0487fd98d1b800273ef843c1ad5dc0f4fc8055658a0698bfe8dfc40651d1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.