Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add 2naive/claude-telegram-topics/plugin install telegram-topicsWrote 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/2naive/claude-telegram-topics/configure)<a href="https://agentmods.dev/skills/2naive/claude-telegram-topics/configure"><img src="https://agentmods.dev/badge/skills/2naive/claude-telegram-topics/configure/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/2naive/claude-telegram-topics/configure"><img src="https://agentmods.dev/badge/skills/2naive/claude-telegram-topics/configure.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.00060 | $0.01115 |
| Opus 5 | $0.00030 | $0.00558 |
| Sonnet 5 | $0.00012 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
configure 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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure telegram-topics
State lives in ~/.claude/channels/telegram-topics/.env (create the directory if
missing). Write the .env with LF line endings (the runtime parser tolerates
CRLF, but LF keeps every shell tool happy too). Keys:
TELEGRAM_BOT_TOKEN— from @BotFather (/newbot)TELEGRAM_GROUP_CHAT_ID— a forum-enabled supergroup id (looks like-100…)TELEGRAM_ALLOWED_USER_IDS— optional CSV of numeric user ids (managed by/telegram-topics:access)
Note: process environment variables take precedence over the .env — if the
user has any TELEGRAM_* of these exported in their shell, warn them that the
exported value wins over what you write here.
Dispatch on the argument
- no argument — Read the
.envand report status: is the token set? is the group id set? Then run Preflight below and show its verdicts. Never print the token value. - a bot token (looks like
123456789:AA…) — write/replaceTELEGRAM_BOT_TOKENin the.env, preserving other keys. Then run Preflight. group <id>— write/replaceTELEGRAM_GROUP_CHAT_ID. Then run Preflight.clear— removeTELEGRAM_BOT_TOKENfrom the.env.
Getting the group id
- In Telegram, create a group, open its settings, and enable Topics (this makes it a forum). 2. Add the bot to the group and promote it to admin with Manage Topics enabled (Telegram does not grant that right by default).
- Send any message in the group, then read the chat id — e.g. add
@userinfobot to the group, or call the Bot API
getUpdatesonce. Forum supergroup ids start with-100.
Preflight (run after both token and group id are set)
Setup mistakes are the most common first-run failure, so validate and report
actionable verdicts. The checks live in the plugin (scripts/preflight.ts)
so they parse the .env exactly like the runtime (CRLF-safe, same precedence)
and the token never appears in a command or output. Run:
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.
- 8d ago First seen · 95 lines · 60 tokens per session scan A 1b590230a85d
configure is a skill published in the GitHub repository 2naive/claude-telegram-topics (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,115 once invoked, about $0.0003 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
tg-alerts
Use when adding Telegram error notifications to any project. Guides through bot creation with @BotFather, chat/channel/forum-topic ID discovery, alert service implementation with deduplication and graceful failure, and framework-specific integration for Python (async/sync) and Node.js.
backend-development
A set of instructions for building server-side code such as APIs and database-backed applications. It uses API contracts, data models, the chosen technology stack, and tests as the project’s reference points.
api-contract-first
A set of rules for designing and changing OpenAPI 3.0 interface contracts. These contracts describe how a frontend and backend communicate, including URLs, fields, errors, and status codes.
zasilkovna
Integrate and manage Zásilkovna (Packeta) shipping for Czech and Slovak logistics. Create shipments, generate labels, track packages, manage pickup points, and configure webhooks using the Zásilkovna API. Covers both the REST API and SOAP API. Includes ready-to-run CLI scripts for all API operations. Context: User…
symfony:doctrine-events
React to Doctrine entity lifecycle in Symfony with attribute listeners (#[AsDoctrineListener]/#[AsEntityListener], ORM 3) and lifecycle callbacks.
symfony:config-env-parameters
Manage Symfony configuration with .env files, parameters, secrets vault, and environment-specific settings.