agentmods.dev

telegram-agent AGENTS.md

telegram-agent AGENTS.md is an instructions file for Codex, OpenCode from Frejixxx/telegram-agent. It costs 1,165 tokens per session, scanned A, original, MIT.

A project guide for coding agents working on a local Telegram tool. It describes the project's purpose, files, architecture, configuration, and main entry points.

In plain words
What is it for?
Use it when developing, debugging, or extending the Telegram agent, its MCP server, setup wizard, authentication, search, digests, or reply features.
Why use it?
It gives an agent the context needed to navigate the codebase and make changes in the right places. This reduces guesswork about how the Telegram tool is structured.

Instructions file for CodexOpenCode

not rated 1 2mo ago A scan 1,165 tokens original MIT
View the source file Frejixxx/telegram-agent
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/frejixxx/telegram-agent/agents-md
Clone the repo
git clone --depth 1 https://github.com/Frejixxx/telegram-agent

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.

agentmods badge for telegram-agent AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/frejixxx/telegram-agent/agents-md.svg)](https://agentmods.dev/instructions/frejixxx/telegram-agent/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/frejixxx/telegram-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/frejixxx/telegram-agent/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,165 This file is loaded in full into every session.
When invoked 1,165 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01165 $0.01165
Opus 5 $0.00583 $0.00583
Sonnet 5 $0.00233 $0.00233
Haiku 4.5 $0.00117 $0.00117

Measured 3d ago against content hash 31fe8aee1e73, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

telegram-agent 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 3d 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 · 111 lines

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.

AGENTS.md

Project Identity

Telegram Agent is a local Codex plugin and MCP server for Telegram setup, inbox triage, dialog lookup, selected-chat context, message search, SQLite-backed digests/search/watchlists, maintainer intelligence, ordinary-user personal briefings, smart inbox ranking, local memory search, secret-safe sensitive search, contact briefs, follow-up tracking, prompt-injection detection, GitHub issue drafts, Codex context packs, local reply drafts, scoped reply sessions, and explicitly authorized sends. It is a CommonJS Node.js project.

Runtime Map

  • MCP entry point: scripts/telegram-agent-server.js.
  • Intelligence/cache module: scripts/intelligence-store.js.
  • Auth metadata module: scripts/auth-store.js.
  • Browser setup wizard: scripts/setup-web.js and scripts/setup-web-ui.js.
  • Demo entry point: scripts/demo.js.
  • Terminal login fallback: scripts/login.js.
  • Codex plugin manifest: .codex-plugin/plugin.json.
  • MCP server config: .mcp.json and .codex/config.toml.
  • Skill instructions loaded by Codex: skills/telegram-agent/SKILL.md.

The MCP server runs over stdio, implements initialize, tools/list, and tools/call, and returns tool output as JSON text content.

Directory Map

  • scripts/: first-party runtime and login code.
  • fixtures/: synthetic demo sources/messages; no real Telegram data.
  • skills/: Codex skill instructions for safe Telegram tool usage.
  • .codex-plugin/: plugin manifest consumed by Codex plugin install/cache.
  • .codex/: local Codex MCP config for this plugin.
  • .github/: GitHub Actions workflows.
  • test/: Node node:test unit tests.
  • node_modules/: vendored dependencies from npm install; do not edit.

Core Architecture

scripts/telegram-agent-server.js owns:

  • MCP tool schemas;
  • Telegram client loading/caching;
  • dialog and entity summaries;
  • message normalization and chat stats;
  • draft file creation/list/delete/send;
  • direct send gate via TELEGRAM_AGENT_ALLOW_SEND;
  • JSON-RPC framing over stdio.

Read the full file on GitHub · 111 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. 3d ago First seen · 111 lines · 1,165 tokens per session scan A 31fe8aee1e73

Subscribe to this mod's changes

telegram-agent AGENTS.md is an instructions file published in the GitHub repository Frejixxx/telegram-agent (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,165 tokens to every session, about $0.0058 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.

Related

Other instructions, from other repositories

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

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens