operate-telegram-ads

operate-telegram-ads is a skill for Claude Code from sh0tn1k/telegram-ads. It costs 77 tokens per session (26,102 once invoked), scanned A, original, MIT.

A controlled tool workflow for operating ads.telegram.org, the Telegram Ads website. It supports reviewing accounts and campaigns, preparing ads, analyzing rejections, and handling campaign changes through human approval.

In plain words
What is it for?
Checking balances and statistics, taking account snapshots, validating ad drafts, reviewing rejections, and approving campaign actions such as changing CPM, managing budgets, starting, stopping, creating, editing, or deleting ads.
Why use it?
It gives the agent a defined way to use Telegram Ads without directly controlling the website or bypassing the tool layer. Approval steps help prevent accidental changes to live ads, budgets, or campaigns.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: built for hermes-agent.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/hermes/.hermes/telegram_ads_phone.txt.

Part of the telegram-ads plugin — 13 skills shipped together

Good fit Checking balances and statistics, taking account snapshots, validating ad drafts, reviewing rejections, and approving campaign actions such as changing CPM, managing budgets, starting, stopping, creating, editing, or deleting ads.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add sh0tn1k/telegram-ads
Claude Code
/plugin install telegram-ads

Made for: Claude Code.

Or install telegram-ads, the plugin that ships this one along with the rest of its 13 skills.

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 operate-telegram-ads

README.md
[![agentmods](https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/operate-telegram-ads/github.svg)](https://agentmods.dev/skills/sh0tn1k/telegram-ads/operate-telegram-ads)
Your own site
<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.

agentmods 80×15 button for operate-telegram-ads

Your own site · 80×15
<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>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 26,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Sonnet 5 · 7 Sept 2026 📄 Read the review
Origin original 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.00077 $0.26102
Opus 5 $0.00039 $0.13051
Sonnet 5 $0.00015 $0.05220
Haiku 4.5 $0.00008 $0.02610

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

Security

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.

skills/operate-telegram-ads/SKILL.md · 1,944 lines

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

  1. Always start a session-touching task with telegram_ads_status or telegram_ads_ensure_login.
  2. Use the most specific tool for the job (see CAPABILITY_MATRIX.md).
  3. Read the envelope's status before anything else.
  4. 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):

  1. Call telegram_ads_login_from_env. It types TELEGRAM_ADS_PHONE from the host .env (never invent a number; never print it unmasked).
  2. Tell the operator the masked number was entered and he must tap Accept in Telegram. Then immediately call telegram_ads_login_wait.
  3. On logged_in, retry the original tool. The Chromium profile keeps the cabinet session.
  4. Only if state=code_required: ask the operator to forward the ads.telegram.org code and call telegram_ads_login_submit_code. Do not invent a code.
  5. Do not drive raw Playwright / a second Chromium on this profile.

Halt-and-ask branch (mandatory during server-side login assist)

Read the full file on GitHub · 1,944 lines

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. 6d ago Changed · +1 lines d2a49cf6c161
  2. 10d ago First seen · 1,943 lines · 77 tokens per session scan E ab4db0e21b75

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens