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 commands/witt3rd/claude-plugins/telegram-next-messagegit clone --depth 1 https://github.com/witt3rd/claude-pluginsWhat 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.00000 | $0.00313 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 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.
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.jsonto 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.jsonwith 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 messagesRead- Read state fileWrite- Update state file
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 · 51 lines · 0 tokens per session scan A c8129d9a302a
telegram-next-message is a command published in the GitHub repository witt3rd/claude-plugins (2 stars, last pushed 10mo 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.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
thread
Manage conversation threads (create, switch, update, delete, show).
handoff
Generate or load a session handoff. Usage: /handoff [create|resume].