egregore: Skill for Claude Code

.claude/skills/telegram-connect/SKILL.md

telegram-connect is a skill for Claude Code from egregore-labs/egregore. It costs 47 tokens per session (1,141 once invoked), scanned A, original, MIT.

A setup process that connects Telegram, a messaging service, to receive notifications from an Egregore project. It creates or links a Telegram group, connects a bot, and stores the group identifier.

In plain words
What is it for?
Use it to enable Telegram notifications, create the notification group, and link the project to the correct chat.
Why use it?
It gives the project a designated place for sending notifications instead of leaving that connection to be configured manually.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is egregore-labs/egregore's own configuration. It tells Claude Code how to work on egregore itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything egregore configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash bin/notify.sh plan group "Telegram connected! 🎉" > tmp/telegram-connect-plan.json.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/telegram-connect/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/egregore-labs/egregore

Made for: Claude Code.

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.

agentmods badge for telegram-connect

README.md
[![agentmods](https://agentmods.dev/badge/skills/egregore-labs/egregore/telegram-connect/github.svg)](https://agentmods.dev/skills/egregore-labs/egregore/telegram-connect)
Your own site
<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.

agentmods 80×15 button for telegram-connect

Your own site · 80×15
<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>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,141 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01141
Opus 5.5 $0.00019 $0.00456
Sonnet 5.5 $0.00009 $0.00228
Haiku 4.5 $0.00005 $0.00114

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

Security

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 24d 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.

.claude/skills/telegram-connect/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 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 ask for the chat ID with a structured question when available and permitted in this session; otherwise ask in plain text:

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."

Read the full file on GitHub · 128 lines

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.

  1. 24d ago Changed · +17 lines bab3dd17b981
  2. 1mo ago First seen · 111 lines · 47 tokens per session scan A 31e26a30f148

Subscribe to this mod's changes

telegram-connect is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 47 tokens to every session and 1,141 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

handoff-protocols

Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…

rohitg00/skillkit · 116 tokens

parallel-investigation

Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…

rohitg00/skillkit · 97 tokens

structured-code-review

Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…

rohitg00/skillkit · 112 tokens

bothread

Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.

AdamACE9/bothread · 66 tokens

git-workflow

Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.

chandrudp29/skillhub · 41 tokens

mflow

Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…

Obed0101/mflow · 77 tokens