What is telegram-next-message?

A command that retrieves the next unprocessed message from Telegram Saved Messages, Telegram's private area for saved messages, and asks what to do with it.

Reviewing one saved message at a time, turning messages into notes, skipping them, detecting whether they contain a URL, video, PDF, or text, and updating processing state.

It provides a repeatable way to work through saved messages while remembering which message was handled last.

telegram-next-message — Command for Claude Code by witt3rd

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.

Clone the repo

git clone --depth 1 https://github.com/witt3rd/claude-plugins

Made for: Claude Code.

Or install azkg, the plugin that ships this one along with the rest of its 18 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/witt3rd/claude-plugins/telegram-next-message/github.svg)](https://agentmods.dev/commands/witt3rd/claude-plugins/telegram-next-message)

Your own site

<a href="https://agentmods.dev/commands/witt3rd/claude-plugins/telegram-next-message"><img src="https://agentmods.dev/badge/commands/witt3rd/claude-plugins/telegram-next-message/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/witt3rd/claude-plugins/telegram-next-message"><img src="https://agentmods.dev/badge/commands/witt3rd/claude-plugins/telegram-next-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 313 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00313
Opus 5.5	$0.00000	$0.00125
Sonnet 5.5	$0.00000	$0.00063
Haiku 4.5	$0.00000	$0.00031

Measured 1mo ago against content hash c8129d9a302a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

telegram-next-message 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 1mo 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.

plugins/azkg/commands/telegram-next-message.md · 51 lines

What it actually says

Telegram: Get Next Unprocessed Message

Retrieve the next unprocessed message from Telegram Saved Messages and present options for handling it.

Usage

/telegram-next-message

Process

Read .telegram_state.json to get the last processed message info
If no messages processed yet, start from 2020-01-01
Fetch next message after the last processed one (limit: 1)
Display the message content with context (date, message ID)
Present options:
- Create a note from this message
- Skip/ignore this message
- Stop processing

After User Decision

If creating a note:

Detect message type (URL, YouTube, PDF, text, etc.)
Suggest appropriate handler command
Wait for user to confirm

If skipping:

Update .telegram_state.json with this message's ID and date
Ask if user wants to continue to next message

If stopping:

Do not update state
Exit workflow

State Management

Always update .telegram_state.json after processing each message:

{
  "last_processed_message_id": <message_id>,
  "last_processed_date": "<ISO_date>",
  "saved_messages_dialog_id": 264837327
}

Commands to Use

mcp__plugin_telegram_telegram__read_messages - Fetch messages
Read - Read state file
Write - Update state file

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.

1mo ago First seen · 51 lines · 0 tokens per session scan A c8129d9a302a

Subscribe to this mod's changes

telegram-next-message is a command published in the GitHub repository witt3rd/claude-plugins (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 313 tokens. 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.

Productivity

ws

Word summary — anything told at N levels, from N words down to 1 word, for anything: a topic ("russian literature"), a URL, YouTube link, file, pasted text, a question, or "this". A leading number sets N (5 by default). Shortcut for the Fabric skill's WordSummary intent.

danielmiessler/LifeOS · 69 tokens

telegram-next-message