Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/telegram-connect/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/telegram-connect)<a href="https://agentmods.dev/skills/egregore-labs/egregore/telegram-connect"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/telegram-connect/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/egregore-labs/egregore/telegram-connect"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/telegram-connect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00990 |
| Opus 5 | $0.00023 | $0.00495 |
| Sonnet 5 | $0.00009 | $0.00198 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
telegram-connect 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 10d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up Telegram as a notification center for your Egregore.
Arguments: $ARGUMENTS (none expected)
When to invoke
Trigger phrases:
- "set up telegram", "connect telegram", "add notifications", "telegram-connect"
- "telegram group", "add telegram", "enable telegram", "link telegram"
- "notification setup", "set up notifications"
Disambiguation:
- "send a message on telegram" → NOT this — use the separate notification
consent protocol in
.claude/context/notification-consent.md - "announce something" → NOT this — use
/announce
Step 1: Check current state
Check for existing telegram_chat_id — it lives in .egregore-state.json (preferred) or egregore.json (legacy):
jq -r '.telegram_chat_id // empty' .egregore-state.json 2>/dev/null || jq -r '.telegram_chat_id // empty' egregore.json 2>/dev/null
If already set, show:
Telegram is already connected.
Chat ID: {chat_id}
Group link: {group_link}
To update it, remove `telegram_chat_id` from .egregore-state.json and run `/telegram-connect` again.
And stop.
Step 2: Guide setup
Read the org slug from egregore.json:
jq -r '.slug // empty' egregore.json 2>/dev/null
If slug is set, generate the deep link with it: https://t.me/Egregore_clbot?startgroup=org_{slug}
If slug is empty, fall back to: https://t.me/Egregore_clbot?startgroup=true
Show:
To set up Telegram notifications:
1. Create a Telegram group for your team
2. Add the bot: {deep_link}
3. The bot will respond with your Chat ID — copy it
4. Get the invite link: group name → Edit → Invite Links → Copy
5. Paste both below
Then use AskUserQuestion to ask for the chat ID:
Chat ID (from the bot's message in your group):
Validate: must be a negative number (e.g., -1001234567890) — reject anything else with "That doesn't look like a Telegram chat ID. It should be a negative number like -1001234567890."
Then use AskUserQuestion to ask for the group invite link:
Group invite link:
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.
- 10d ago First seen · 111 lines · 47 tokens per session scan A 31e26a30f148
telegram-connect is a skill published in the GitHub repository egregore-labs/egregore (289 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 990 once invoked, about $0.0002 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-30.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
xiaohongshu-image-creator
An image-making assistant for Xiaohongshu, a Chinese social platform for lifestyle, product, and educational posts. It creates vertical covers and supporting images matched to the post’s topic, audience, and visual style.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…