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 eqba1/telegram-bot-mcp --skill telegram-channel-reportgit clone --depth 1 https://github.com/eqba1/telegram-bot-mcpWrote 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/eqba1/telegram-bot-mcp/telegram-channel-report)<a href="https://agentmods.dev/skills/eqba1/telegram-bot-mcp/telegram-channel-report"><img src="https://agentmods.dev/badge/skills/eqba1/telegram-bot-mcp/telegram-channel-report/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/eqba1/telegram-bot-mcp/telegram-channel-report"><img src="https://agentmods.dev/badge/skills/eqba1/telegram-bot-mcp/telegram-channel-report.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.00081 | $0.00691 |
| Opus 5 | $0.00041 | $0.00345 |
| Sonnet 5 | $0.00016 | $0.00138 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
telegram-channel-report 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 9d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram Channel Report
Produce subscriber-growth reports and manage posts for a Telegram channel via
the telegram-channel MCP server.
Daily stats report
-
Call
snapshot_members. It records today's subscriber count and returns the change since the previous recorded snapshot. -
Call
get_growth_historywithlimit: 14to get recent trend data. -
Report in this shape — keep it to a few lines, no headers:
- Channel name and current subscriber count
- Change since the last snapshot, with direction (
+12/-3/ unchanged) - Trend over the recorded window: net change and whether growth is accelerating, steady, or slowing
- One plain-language observation, only if the data supports one
-
When
previousisnull, say plainly that this is the first measurement and that comparisons start from the next run. Do not invent a baseline.
Match the user's language. If the user writes in Persian, report in Persian.
Reading the numbers honestly
- The Bot API reports subscriber count only. It cannot report post views, forwards, or reach — never present those as available.
- A single day's delta is noise. Do not describe one day's movement as a trend.
- If snapshots skip days, the
changefield spans that whole gap. Check thedatevalues inget_growth_historybefore calling a number "daily growth".
Managing posts
send_postpublishes a new post. Show the user the exact text and get confirmation before publishing — a channel post reaches every subscriber.edit_postreplaces post text. Only posts the bot itself published can be edited.pin_postpins or unpins (passunpin: true).delete_postis irreversible. Confirm themessage_idwith the user first, and never delete a post the user did not explicitly name.
Troubleshooting
| Error mentions | Cause | Fix to suggest |
|---|---|---|
chat not found |
Wrong channel id, or bot was never added | Add the bot as a channel admin; for private channels use the numeric id |
not enough rights |
Bot lacks the needed admin permission | Grant "Post Messages" / "Edit Messages" in channel admin settings |
bot token / Unauthorized |
Token missing or revoked | Re-check the token in the plugin's config.json |
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.
- 9d ago First seen · 68 lines · 81 tokens per session scan A 8dee8ce95a22
telegram-channel-report is a skill published in the GitHub repository eqba1/telegram-bot-mcp (0 stars, last pushed 21d ago), licensed MIT. It adds 81 tokens to every session and 691 once invoked, about $0.0004 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
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
remindme
⏰ simple Telegram reminders for OpenClaw. cron, zero dependencies.
headless-bot
Nested swiss-knife reference for creating and operating a headless LingTai bot project without opening the TUI. Start from lingtai-tui spawn, then apply the relevant addon/MCP wiring, keep secrets in sidecar files, copy preset policy by referencing existing presets instead of copying preset JSON files, refresh or…
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…
telegram
Multi-bot Telegram bridge — routes messages between Telegram and Claude tmux sessions.
ambient-context
Use when the user refers to what they were working on, asks to catch up, mentions their day, week, record or Ambient Context, or when a task needs to know what happened recently on this Mac. Reads the Ambient Context record through its MCP tools and says how much of it to read.