Borrowing it
Nothing to install: this file belongs to godagoo/claude-telegram-relay. 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/godagoo/claude-telegram-relay/master/CLAUDE.mdgit clone --depth 1 https://github.com/godagoo/claude-telegram-relayWrote 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/instructions/godagoo/claude-telegram-relay/claude-md)<a href="https://agentmods.dev/instructions/godagoo/claude-telegram-relay/claude-md"><img src="https://agentmods.dev/badge/instructions/godagoo/claude-telegram-relay/claude-md/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/instructions/godagoo/claude-telegram-relay/claude-md"><img src="https://agentmods.dev/badge/instructions/godagoo/claude-telegram-relay/claude-md.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.02380 | $0.02380 |
| Opus 5 | $0.01190 | $0.01190 |
| Sonnet 5 | $0.00476 | $0.00476 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade C, and why
claude-telegram-relay CLAUDE.md scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Bun not installed → `curl -fsSL https://bun.sh/install | bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bun not installed → `curl -fsSL https://bun.sh/install | bash` How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Telegram Relay — Setup Guide
Claude Code reads this file automatically. Walk the user through setup one phase at a time. Ask for what you need, configure everything yourself, and confirm each step works before moving on.
How This Works
This project turns Telegram into a personal AI assistant powered by Claude.
The user cloned this repo (or gave you the link). Your job: guide them through setup conversationally. Ask questions, save their answers to .env, test each step, move on.
Do not dump all phases at once. Start with Phase 1. When it works, move to Phase 2. Let the user control the pace.
If this is a fresh clone, run bun run setup first to install dependencies and create .env.
Phase 1: Telegram Bot (~3 min)
You need from the user:
- A Telegram bot token from @BotFather
- Their personal Telegram user ID
What to tell them:
- Open Telegram, search for @BotFather, send
/newbot - Pick a display name and a username ending in "bot"
- Copy the token BotFather gives them
- Get their user ID by messaging @userinfobot on Telegram
What you do:
- Run
bun run setupif.envdoes not exist yet - Save
TELEGRAM_BOT_TOKENandTELEGRAM_USER_IDin.env - Run
bun run test:telegramto verify — it sends a test message to the user
Done when: Test message arrives on Telegram.
Phase 2: Database & Memory — Supabase (~12 min)
Your bot's memory lives in Supabase: conversation history, facts, goals, and semantic search.
Step 1: Create Supabase Project
You need from the user:
- Supabase Project URL
- Supabase anon public key
What to tell them:
- Go to supabase.com, create a free account
- Create a new project (any name, any region close to them)
- Wait ~2 minutes for it to provision
- Go to Project Settings > API
- Copy: Project URL and anon public key
What you do:
- Save
SUPABASE_URLandSUPABASE_ANON_KEYto.env
Step 2: Connect Supabase MCP
This lets Claude Code manage the database directly — run queries, deploy functions, apply migrations.
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 · 268 lines · 2,380 tokens per session scan C f06fa65e6e67
claude-telegram-relay CLAUDE.md is an instructions file published in the GitHub repository godagoo/claude-telegram-relay (326 stars, last pushed 6mo ago), licensed MIT. It adds 2,380 tokens to every session, about $0.0119 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.