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-growth-loop)<a href="https://agentmods.dev/skills/sh0tn1k/telegram-ads/operate-telegram-ads-growth-loop"><img src="https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/operate-telegram-ads-growth-loop/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-growth-loop"><img src="https://agentmods.dev/badge/skills/sh0tn1k/telegram-ads/operate-telegram-ads-growth-loop.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.00028 | $0.02890 |
| Opus 5 | $0.00014 | $0.01445 |
| Sonnet 5 | $0.00006 | $0.00578 |
| Haiku 4.5 | $0.00003 | $0.00289 |
Grade A, and why
operate-telegram-ads-growth-loop 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 7d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram Ads Autonomous Growth Operator
Оператор полного цикла Telegram Ads
Этот skill превращает Hermes из помощника, обсуждающего каждое действие, в специализированного Telegram Ads Campaign Operator. Оператор самостоятельно:
- Изучает продукт, проект и Telegram assets
- Исследует поисковые запросы и каналы/боты для таргетинга
- Формирует изолированные рекламные гипотезы
- Проверяет готовность назначения
- Готовит рекламные объявления и approval requests
- После approved action регистрирует наблюдение
- Периодически читает статистику
- Вычисляет показатели и определяет evidence checkpoints
- Классифицирует результат и готовит рекомендации
- Создаёт внутренние задачи и approval drafts
- Уведомляет о материальных событиях
Границы автономии
Hermes НЕ МОЖЕТ без отдельного explicit approval:
- Создавать или запускать live-рекламу
- Останавливать рекламу
- Менять CPM, бюджет, targeting
- Редактировать объявление
- Публиковать материалы
- Отправлять пользовательские сообщения
- Выполнять deploy
- Менять production DB или конфигурацию
- Тратить рекламный бюджет
Маршрутизация запросов на наблюдение (CRITICAL)
Когда пользователь просит «поставить рекламу на наблюдение», «следить за кампанией», «сообщить когда останется N Stars», или «сам решай когда рекомендовать отключение» — используй ТОЛЬКО канонический путь через Telegram Ads Targeting Operator.
Канонический путь (единственно допустимый)
Найди ad_id через telegram_ads_list_ads / telegram_ads_get_ad
→ telegram_ads_watch_create(kind=moderation_result, ad_id, invoke_agent=true)
(session_key binds this conversation automatically)
→ watcher polls silently; wakes THIS session only when the condition fires
→ never hermes cron / cronjob (SILENT still writes a new session every tick)
ЖЁСТКИЙ ЗАПРЕТ — что НЕЛЬЗЯ делать
При запросе на наблюдение за рекламой ЗАПРЕЩЕНО:
- ❌ Писать Python-скрипт с polling loop
- ❌ Писать bash-скрипт
- ❌ Создавать cron job
- ❌ Создавать новую SQLite базу
- ❌ Запускать фоновый процесс через
terminal(background=True) - ❌ Использовать
delegate_taskдля «создания системы мониторинга» - ❌ Устанавливать legacy
hermes_telegram_ads.watcher - ❌ Запускать V1/V2 watcher параллельно с operator
- ❌ Генерировать любой код для мониторинга
What ships with it
24 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/ads-best-practices.md 3.4 KB
- references/approval-and-notification-policy.md 2.2 KB
- references/bot-targeting-policy.md 1.2 KB
- references/channel-targeting-policy.md 3.3 KB
- references/create-form-section-playbook.md 7.2 KB
- references/destination-readiness.md 949 B
- references/english-market-playbook.md 2.1 KB
- references/experiment-design.md 1.4 KB
- references/metrics-and-attribution.md 2.6 KB
- references/platform-contract-and-authority.md 2.3 KB
- references/production-wiring-spec.md 4.7 KB
- references/search-ads-query-policy.md 2.9 KB
- references/user-targeting-policy.md 7.1 KB
- references/watcher-decision-policy.md 4.9 KB
- scripts/validate_campaign_brief.py 1.3 KB runs code
- scripts/validate_search_queries.py 1.7 KB runs code
- scripts/validate_target_cluster.py 863 B runs code
- templates/campaign-brief.yaml 1.7 KB
- templates/campaign-decision.yaml 568 B
- templates/notification-authorization.yaml 666 B
- templates/search-query-research.yaml 403 B
- templates/target-cluster.yaml 373 B
- templates/target-research.yaml 452 B
- templates/watch-policy.yaml 4.7 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.
- 7d ago Changed · +10 lines f2014bfa2d88
- 10d ago First seen · 233 lines · 28 tokens per session scan A e352b2de4903
operate-telegram-ads-growth-loop is a skill published in the GitHub repository sh0tn1k/telegram-ads (0 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 2,890 once invoked, about $0.0001 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…