telegram-ads-create-ops

telegram-ads-create-ops is a skill for Claude Code from sh0tn1k/telegram-ads. It costs 112 tokens per session (1,454 once invoked), scanned A, original, MIT.

A procedure for creating Telegram Ads through typed tools, including account and budget checks, placement rules, draft validation, and after-creation verification.

In plain words
What is it for?
Use it when creating, submitting, testing, or debugging Telegram Ads and checking whether a watcher should be registered afterward.
Why use it?
It reduces mistakes caused by stale balances, unsupported media, incorrect CPMs, failed confirmations, or unclear ad status.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

Good fit Use it when creating, submitting, testing, or debugging Telegram Ads and checking whether a watcher should be registered afterward.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sh0tn1k/telegram-ads/telegram-ads-create-ops
Install

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.

Any agent
npx skills add sh0tn1k/telegram-ads --skill telegram-ads-create-ops
Clone the repo
git clone --depth 1 https://github.com/sh0tn1k/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 telegram-ads-create-ops

README.md
[![agentmods](https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/telegram-ads-create-ops/github.svg)](https://agentmods.dev/skills/sh0tn1k/telegram-ads/telegram-ads-create-ops)
Your own site
<a href="https://agentmods.dev/skills/sh0tn1k/telegram-ads/telegram-ads-create-ops"><img src="https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/telegram-ads-create-ops/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-create-ops

Your own site · 80×15
<a href="https://agentmods.dev/skills/sh0tn1k/telegram-ads/telegram-ads-create-ops"><img src="https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/telegram-ads-create-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,454 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.
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.00112 $0.01454
Opus 5 $0.00056 $0.00727
Sonnet 5 $0.00022 $0.00291
Haiku 4.5 $0.00011 $0.00145

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

Security

Grade A, and why

telegram-ads-create-ops 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 9d 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/telegram-ads-create-ops/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Telegram Ads Create Ops

Class-level runtime ops for the typed create path. Strategy/copy still live in prepare-and-manage-tg-ads; full procedural order in create-telegram-ads-campaign-workflow. This skill stores what the live tools actually do when the docs/skills drift.

When to use

  • the operator: create / submit / test ad (any placement, any cabinet).
  • Confirmation mint fails or returns unknown tool.
  • Screenshot / draft prepare fails.
  • After apply: no ad_id, weird status, balance moved, watcher questions.

Happy path (confirmed)

  1. Pre-mutation 4-step: list_accountschoose_accountcurrent_account (prefer account_ref_source: reconciled) → get_account_budget.
    • Never trust list_accounts.balance. Example 2026-07-16: Example Bot list=⭐0, live=⭐1164.
  2. Placement gate: channels keeps text/media; search strips text/media; bots strips media.
  3. STARS bot cabinets (Example Bot): start CPM ≥ 65 for new ads (older ads at 50 are not a floor).
  4. Test defaults: budget=100, initial_active=false, small target set.
  5. estimate_cpmvalidate_adprepare_ad_draft(screenshot_name="….png"). Before validate_ad: run telegram_ads_prepare_copy_variants on the ad text — it enforces single-line ≤160 (see pitfall 8).
  6. Approval from the operator (high-level "создай … подтверждаю" is enough only after draft is fixed and shown or explicitly within stated scope).
  7. Mint confirmation: telegram_ads_create_ad(draft=…) without confirmation_id.
  8. Apply immediately with identical draft + confirmation_id (TTL ~300s, single-use, fingerprint-bound).
  9. Resolve ad_id: list_ads match title (apply may only return redirect_to: /account).
  10. Verify: get_ad, balance transfer_to_ad (−budget allocation, not spend).
  11. Watch: telegram_ads_register_campaign_watch(ad_id=…, project_id=…, auto_mutations=false).

Critical pitfalls

1. prepare_approval_request(tool="create_ad") → Unknown tool

Read the full file on GitHub · 135 lines

Files

What ships with it

1 file 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.

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. 9d ago First seen · 135 lines · 112 tokens per session scan A 2abad87c0c18

Subscribe to this mod's changes

telegram-ads-create-ops is a skill published in the GitHub repository sh0tn1k/telegram-ads (0 stars, last pushed 8d ago), licensed MIT. It adds 112 tokens to every session and 1,454 once invoked, about $0.0006 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