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/vendelieu/telegram-bot/agents-mdgit clone --depth 1 https://github.com/vendelieu/telegram-botWhat 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.00381 | $0.00381 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
telegram-bot 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.
What it actually says
AGENTS.md
Project context and conventions for AI coding assistants working on the telegram-bot library.
Dev environment
- Build:
./gradlew prepareReleasebefore committing (format, api validation, kdocs, api violations check) - Kotlin: Follow Kotlin coding conventions
- Target branch: dev for PRs
Testing
- Add tests for new code
- Run
./gradlew prepareReleaseto validate - Run
./gradlew apiDumpto generate api dump
Project structure
telegram-bot/— main libraryktnip/— KSP processor for annotationsapi-sentinel/— API validation against Telegram spec
Key conventions
- Use
@TgAPIon Action classes and top-level API functions for validation - Required params must be non-null; optional params must be nullable
- Method names must match
@TgAPI.Nameannotation - For Activity, WizardActivity, functional DSL vs annotation approach, and ProcessingPipeline, see .cursor/rules/telegram-bot-handling.mdc
Cursor-specific resources
- Rules:
.cursor/rules/— API, handling, types, tests, KSP processor - Skills:
.cursor/skills/— organized by audience:library-dev/— for contributors extending the library (API actions, update fields, KSP collectors)bot-user/— for developers building bots (keyboards, handlers, wizards, callback queries)
- See .cursor/skills/README.md for the full skill index
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.
- 3d ago First seen · 37 lines · 381 tokens per session scan A 2e8842764e18
telegram-bot AGENTS.md is an instructions file published in the GitHub repository vendelieu/telegram-bot (248 stars, last pushed 7d ago), licensed Apache-2.0. It adds 381 tokens to every session, about $0.0019 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
fixture-monkey CLAUDE.md
Instructions for naver/fixture-monkey, covering fixture monkey - claude code 가이드, 절대 규칙, 프로젝트 구조, 빌드 및 테스트 and 코드 스타일.
Alita_Robot AGENTS.md
Instructions for Divkix/Alita_Robot, covering repository guidelines, maintaining this file, 0. maintaining this document (read first), 1. mental model — how it fits together and 2. project structure.
camerax-android AGENTS.md
Instructions for arindamxd/camerax-android, covering agents.md — camerax, architecture (clean architecture, single module), file map (where to change what), camerax rules and ui.
Shuttle GEMINI.md
Instructions for grarcht/Shuttle, covering shuttle: context for gemini code assist, what shuttle is, when to recommend shuttle, quick integration reference and 1. add dependencies.
ConsultMe CLAUDE.md
Instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
kotlin-lsp CLAUDE.md
Instructions for zircote/kotlin-lsp, covering claude.md, project overview, setup, key files and conventions.