telegram-ads-mcp: Instructions file for Codex

AGENTS.md

telegram-ads-mcp AGENTS.md is an instructions file for Codex, OpenCode from zai-one/telegram-ads-mcp. It costs 408 tokens per session, scanned A, original, no licence file.

Repository instructions for working on zai-one/telegram-ads-mcp, including its agent playbook, currency handling, authentication, write-safety gate, and list fields. Telegram Ads is Telegram's advertising platform, and MCP is a way for assistants to use external tools.

In plain words
What is it for?
Use it when working in the telegram-ads-mcp project, especially for authentication, currency, list-field handling, and protected write operations.
Why use it?
It gives coding agents the project-specific rules they need before changing or querying this repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is zai-one/telegram-ads-mcp's own configuration. It tells Codex and OpenCode how to work on telegram-ads-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything telegram-ads-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zai-one/telegram-ads-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zai-one/telegram-ads-mcp/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/zai-one/telegram-ads-mcp

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-ads-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/zai-one/telegram-ads-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/zai-one/telegram-ads-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/zai-one/telegram-ads-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/zai-one/telegram-ads-mcp/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.

agentmods 80×15 button for telegram-ads-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zai-one/telegram-ads-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/zai-one/telegram-ads-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 408 This file is loaded in full into every session.
When invoked 408 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.1 $0.00408 $0.00408
Opus 5.5 $0.00163 $0.00163
Sonnet 5.5 $0.00082 $0.00082
Haiku 4.5 $0.00041 $0.00041

Measured 11d ago against content hash bfe80e6afe4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

telegram-ads-mcp 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 11d 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 · 22 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 11d ago Changed · -110 lines · -2,968 tokens per session scan C → A bfe80e6afe4f
  2. 13d ago Changed · +12 lines · +393 tokens per session ee969eaa7aba
  3. 14d ago Changed · +17 lines · +327 tokens per session 5e515ed35e31
  4. 1mo ago Changed · +34 lines · +1,350 tokens per session scan A → C 39f46bb108a4
  5. 1mo ago First seen · 69 lines · 1,306 tokens per session scan A d7920aa2115b

Subscribe to this mod's changes

telegram-ads-mcp AGENTS.md is an instructions file published in the GitHub repository zai-one/telegram-ads-mcp (4 stars, last pushed 12d ago), with no licence file. It adds 408 tokens to every session, about $0.0016 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.

Related

Other instructions, from other repositories