What is ChatGPT-to-Telegram-MCP AGENTS.md?

A set of project instructions for maintaining an OAuth-protected service that lets an AI client read recent Telegram sending history and publish deduplicated posts to one channel.

Understanding the repository, preserving the Telegram service's interfaces, and guiding implementation and tests.

It gives an agent the project structure, public tool contracts, setup commands, and implementation rules needed to change the repository safely.

How d8rt8v/ChatGPT-to-Telegram-MCP configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to d8rt8v/ChatGPT-to-Telegram-MCP. 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/d8rt8v/ChatGPT-to-Telegram-MCP/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/d8rt8v/ChatGPT-to-Telegram-MCP

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/d8rt8v/chatgpt-to-telegram-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/d8rt8v/chatgpt-to-telegram-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/d8rt8v/chatgpt-to-telegram-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/d8rt8v/chatgpt-to-telegram-mcp/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/d8rt8v/chatgpt-to-telegram-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/d8rt8v/chatgpt-to-telegram-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 997 This file is loaded in full into every session.

When invoked 997 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00997	$0.00997
Opus 5.5	$0.00399	$0.00399
Sonnet 5.5	$0.00199	$0.00199
Haiku 4.5	$0.00100	$0.00100

Measured 2mo ago against content hash 8abad44a6ed6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ChatGPT-to-Telegram-MCP AGENTS.md 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 2mo 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.

AGENTS.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Project overview

This repository contains an OAuth-protected Streamable HTTP MCP server deployed on Cloudflare Workers. It allows ChatGPT or another MCP client to read this server's recent Telegram send history and publish deduplicated posts to one fixed Telegram channel.

The public MCP tools are:

get_previous_messages: reads up to 100 D1 records from the previous 48 hours.
send_message: reserves a text fingerprint and canonical source URLs in D1, publishes through the Telegram Bot API, and records the result.

Treat these tool names and their input/output shapes as public interfaces. Preserve backward compatibility unless the task explicitly requests a breaking change.

Repository map

src/index.js: MCP server, tool schemas, Worker entrypoint, and OAuth provider configuration.
src/oauth-handler.js: GitHub OAuth sign-in, allowlist enforcement, consent page, and health endpoint.
src/storage.js: D1 history, reservations, duplicate lookup, and send-state updates.
src/dedupe.js: text fingerprints and canonical source URLs.
src/telegram.js: Telegram Bot API client.
migrations/: additive D1 migrations.
test/: Node.js tests.
wrangler.example.jsonc and .env.example: public configuration templates.

Setup and commands

Use Node.js 20 or newer and install dependencies with npm ci.

For local development, copy wrangler.example.jsonc to wrangler.jsonc and .env.example to .env, then replace every placeholder. Both live files are ignored by Git.

npm test: run the complete Node.js test suite.
npm run check: check JavaScript syntax.
npm run dev: start the local Worker.
npm run db:migrate:local: apply D1 migrations to the local DB binding.
npm run db:migrate:remote: apply migrations to the configured remote D1 database.
npm run deploy: deploy the Worker.
npm run secrets:push: upload .env values as Cloudflare Worker secrets.

Remote migrations, secret uploads, and deployments change external state. Run them only when the user explicitly requests that action. A Wrangler --dry-run build is appropriate for local verification.

Read the full file on GitHub · 71 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.

2mo ago First seen · 71 lines · 997 tokens per session scan A 8abad44a6ed6

Subscribe to this mod's changes

ChatGPT-to-Telegram-MCP AGENTS.md is an instructions file published in the GitHub repository d8rt8v/ChatGPT-to-Telegram-MCP (1 stars, last pushed 3mo ago), licensed MIT. It adds 997 tokens to every session, about $0.0040 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-31.

ChatGPT-to-Telegram-MCP AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ChatGPT-to-Telegram-MCP AGENTS.mdd8rt8v/ChatGPT-to-Telegram-MCP	Instructions file	1	3mo ago	MIT	A	997	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

ChatGPT-to-Telegram-MCP: Instructions file for Codex