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/will-17173/telegram-cli/agents-mdgit clone --depth 1 https://github.com/will-17173/telegram-cliWhat 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.00907 | $0.00907 |
| Opus 5 | $0.00453 | $0.00453 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
telegram-cli 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 53 lines · 907 tokens per session scan A cb01a207157c
telegram-cli AGENTS.md is an instructions file published in the GitHub repository will-17173/telegram-cli (6 stars, last pushed 15d ago), licensed GPL-3.0. It adds 907 tokens to every session, about $0.0045 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.
Other instructions, from other repositories
tg-ws-proxy-rs AGENTS.md
Instructions for valnesfjord/tg-ws-proxy-rs, covering agents.md, what this project is, repository layout, build, test, lint and releases.
mytg CLAUDE.md
Claude Code instructions for eqyv/mytg, covering claude.md — project context for ai assistants, what this project is, tech stack, architecture overview and key design decisions.
fast-mcp-telegram CLAUDE.md
Instructions for alexeyleshchenko/fast-mcp-telegram, covering fast-mcp-telegram, session corrections and 2026-05-27.
ZhiWei CLAUDE.md
Instructions for ntygod/ZhiWei, covering claude.md, project overview, build & development commands, backend and frontend.
telegram-search copilot-instructions.md
Copilot instructions for groupultra/telegram-search, covering copilot instructions for telegram-search, architecture essentials, dev workflows, conventions and patterns and where to look for examples.
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).