Borrowing it
Nothing to install: this file belongs to leynier/telegram-cli. 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/leynier/telegram-cli/main/AGENTS.mdgit clone --depth 1 https://github.com/leynier/telegram-cliWrote 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/leynier/telegram-cli/agents-md)<a href="https://agentmods.dev/instructions/leynier/telegram-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/leynier/telegram-cli/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.
<a href="https://agentmods.dev/instructions/leynier/telegram-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/leynier/telegram-cli/agents-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.00526 | $0.00526 |
| Opus 5.5 | $0.00210 | $0.00210 |
| Sonnet 5.5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00053 | $0.00053 |
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 1mo 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Purpose
Build and maintain clitg as a deterministic, non-interactive Telegram CLI for AI agents. Treat
its stdout JSON, schemas, exit codes, safety checks, and capability manifest as public APIs.
Tooling
- Use uv for all Python and dependency operations.
- Create project metadata with
uv init; add or remove dependencies withuv addanduv remove. - Commit
uv.lockand.python-version. Do not hand-edit dependency arrays. - Run Python commands through
uv run. - Use Ruff for formatting and linting, and ty for type checking.
- Write code, comments, documentation, tests, and commit messages in English.
Product invariants
- Never add interactive prompts. All values must arrive through options, environment variables, files, or explicitly selected stdin.
- Emit operational successes and failures as schema-versioned JSON or JSONL on stdout.
- Keep stderr empty unless redacted verbose diagnostics were explicitly requested.
- Never print or log API hashes, login codes, passwords, auth keys, or session material.
- Do not mark messages read during list, get, search, resolve, schema, or capability operations.
- Resolve ambiguous peers by returning candidates; never guess a mutation target.
- Support
--dry-runfor every mutation. Preserve exact confirmation and critical-token checks. - Treat unknown raw methods as critical until their risk has been reviewed.
- Keep personal sessions, credentials, Telegram data, and real account identifiers out of tests.
Architecture
- Keep Typer presentation, application services, storage, and Telethon integration separated.
- Keep Telethon and dynamic TL values at adapter boundaries; use typed Pydantic models internally.
- Prefer the friendly Telethon API for dedicated commands and the generated TL registry for raw coverage.
- Update generated schemas and capabilities whenever public models or Telethon change.
- Preserve schema
0.2across patch releases. A breaking contract requires a new minor schema and a coordinated skill update.
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.
- 1mo ago First seen · 50 lines · 526 tokens per session scan A ee81727cbc11
telegram-cli AGENTS.md is an instructions file published in the GitHub repository leynier/telegram-cli (8 stars, last pushed 4d ago), licensed MIT. It adds 526 tokens to every session, about $0.0021 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.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.