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.
npx agentmods add instructions/kfastov/tgcli/agents-mdgit clone --depth 1 https://github.com/kfastov/tgcliWhat 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 | $0.00661 | $0.00661 |
| Opus 5 | $0.00331 | $0.00331 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
tgcli 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 2d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
mcp-server.js: MCP HTTP server built with@modelcontextprotocol/sdk, registering the Telegram tools (listChannels,searchChannels,getChannelMessages,scheduleMessageSync,listMessageSyncJobs).telegram-client.js: Domain logic for MTProto login, dialog traversal, and message helpers.client.js: Example CLI harness for manual testing without the MCP layer.message-sync-service.js: Background worker that archives messages into a local SQLite database.- Store location: OS app-data dir (tgcli store; override with
TGCLI_STORE); keep runtime artifacts out of version control. - Documentation lives in
README.mdandLIBRARY.md; configuration relies on environment variables and the tgcli store.
Build, Test, and Development Commands
npm install: Restore dependencies wheneverpackage-lock.jsonchanges.npm start: Boot the MCP server onhttp://localhost:8080/mcpusing Streamable HTTP transport; first run drives the Telegram login flow.node client.js: Run the sample script to exercise the client API and inspect dialog listings.npm run build: Currently a no-op placeholder—extend it only if a transpile/bundle step is introduced.npm test: Placeholder that echoes a notice; replace with real checks once tests exist.
Coding Style & Naming Conventions
- Use ES modules with semicolons, two-space indentation, and
camelCaseidentifiers. - Keep tool names descriptive and aligned with Telegram operations (
listChannels,searchChannels, etc.). - Emit log lines that explain side effects (login state, MTProto calls, sync progress) and reference chat IDs/titles.
- Keep message sync queue strictly sequential; jobs transition through
pending → in_progress → idleand may move toerrorif retries are needed. - Store secrets in
.env; never hard-code API credentials or session paths in commits.
Testing Guidelines
- Add coverage when extending
telegram-client.jsormessage-sync-service.jsby mocking MTProto responses to validate session reuse and message archiving. - Name new test files
<module>.test.jsundertests/or co-locate in__tests__/; makenpm testexecute them. - Before pushing, run your test suite and a smoke
npm startto verify authentication prompts and cache initialization remain intact.
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.
- 2d ago First seen · 40 lines · 661 tokens per session scan A 6557263b51cd
tgcli AGENTS.md is an instructions file published in the GitHub repository kfastov/tgcli (42 stars, last pushed 1mo ago), licensed MIT. It adds 661 tokens to every session, about $0.0033 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 instructions, from other repositories
mcp-steroid CLAUDE.md
Instructions for jonnyzzz/mcp-steroid, covering claude.md, agents.md, design philosophy, recursive context lookup (do this before sub-folder work), sub-folder guides and must do.
telegram-search AGENTS.md
AGENTS.md instructions for groupultra/telegram-search, covering project coded agent guide, tech stack (by surface), structure & responsibilities, key path index (what lives where) and commands (pnpm with filters).
nopua AGENTS.md
Instructions for wuji-labs/nopua, covering nopua · codex 入仓规则, 一 · 项目定位, 二 · 起手必读, 三 · 工程与研究纪律 and 四 · 对外署名.
skills CLAUDE.md
Instructions for mixedbread-ai/skills, covering mixedbread skills, repository structure, conventions, adding a new skill and testing a skill.
governed-agent-skills CLAUDE.md
Instructions for Ezra144israel/governed-agent-skills: Read AGENTS.md. It governs this repository.
video-podcast-maker AGENTS.md
AGENTS.md instructions for Agents365-ai/video-podcast-maker, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.