Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sh0tn1k/telegram-ads/plugin install telegram-adsWrote 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/skills/sh0tn1k/telegram-ads/operate-telegram-ads)<a href="https://agentmods.dev/skills/sh0tn1k/telegram-ads/operate-telegram-ads"><img src="https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/operate-telegram-ads/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/skills/sh0tn1k/telegram-ads/operate-telegram-ads"><img src="https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/operate-telegram-ads.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.00077 | $0.26102 |
| Opus 5 | $0.00039 | $0.13051 |
| Sonnet 5 | $0.00015 | $0.05220 |
| Haiku 4.5 | $0.00008 | $0.02610 |
Grade A, and why
operate-telegram-ads 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 6d 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 — 1,944 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate Telegram Ads
You drive ads.telegram.org only through the telegram_ads_* tools. You never
open ads.telegram.org yourself, never run Playwright/Chromium/Xvfb, never pick a
DISPLAY, never click the UI, and never call the internal /api. The tool layer
owns the browser, the login session, account-token masking, and confirmation
tokens.
When to use
- Reviewing cabinets, balances, campaigns, stats, or rejections.
- Taking a daily/weekly snapshot of all accounts.
- Preparing, validating, or previewing ad drafts.
- Changing CPM, adding/withdrawing budget, starting/stopping, creating, editing, or deleting ads — call the mutating tool; Telegram buttons confirm it.
- Working with pixel conversion events (Stars cabinets).
When NOT to use
- The action isn't about Telegram Ads.
- A tool returns
not_implemented/forbidden— do not work around it.
Mandatory tool path
- Always start a session-touching task with
telegram_ads_statusortelegram_ads_ensure_login. - Use the most specific tool for the job (see CAPABILITY_MATRIX.md).
- Read the envelope's
statusbefore anything else. - For any mutation, follow the approval flow below — never assume approval.
login_required handling
If any tool returns status: "login_required" (or the operator asks to log in):
- Call
telegram_ads_login_from_env. It typesTELEGRAM_ADS_PHONEfrom the host.env(never invent a number; never print it unmasked). - Tell the operator the masked number was entered and he must tap Accept in
Telegram. Then immediately call
telegram_ads_login_wait. - On
logged_in, retry the original tool. The Chromium profile keeps the cabinet session. - Only if
state=code_required: ask the operator to forward the ads.telegram.org code and calltelegram_ads_login_submit_code. Do not invent a code. - Do not drive raw Playwright / a second Chromium on this profile.
Halt-and-ask branch (mandatory during server-side login assist)
What ships with it
23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/acceptance-readonly-protocol.md 10 KB
- references/active-runtime-patch-verification.md 6.2 KB
- references/ad-detail-media-parser.md 4.3 KB
- references/branch-preflight-recipe.md 6.0 KB
- references/cabinet-scoped-campaign-identity.md 1.3 KB
- references/code-patch-live-verification-gotcha.md 4.6 KB
- references/creative-options-and-cpm-modifiers.md 12 KB
- references/feature-branch-integration.md 11 KB
- references/hermes-telegram-ads-update-protocol.md 26 KB
- references/legacy-action-mapping.md 6.2 KB
- references/login-flow-patterns.md 7.1 KB
- references/login-flow-process-isolation.md 21 KB
- references/login-policy.md 8.4 KB
- references/media-channel-create-postcreate-discrepancy.md 3.1 KB
- references/media-live-flow-create-verification.md 2.4 KB
- references/media-placement-compatibility.md 4.3 KB
- references/media-source-and-detail-parser-pitfalls.md 2.4 KB
- references/telegram-tools-ui-registry-chain.md 9.1 KB
- references/test-campaign-cleanup-audit.md 6.3 KB
- references/three-layer-model.md 3.1 KB
- references/typed-wrapper-arg-name-collision.md 5.2 KB
- references/typed-wrapper-envelope-diagnostics.md 3.8 KB
- references/typed-wrapper-event-loop-lifecycle.md 4.6 KB
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.
- 6d ago Changed · +1 lines d2a49cf6c161
- 10d ago First seen · 1,943 lines · 77 tokens per session scan E ab4db0e21b75
operate-telegram-ads is a skill published in the GitHub repository sh0tn1k/telegram-ads (0 stars, last pushed 9d ago), licensed MIT. It adds 77 tokens to every session and 26,102 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…