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.
npx skills add ilyautov/small-business-ru --skill call-listgit clone --depth 1 https://github.com/ilyautov/small-business-ruWrote 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/ilyautov/small-business-ru/call-list)<a href="https://agentmods.dev/skills/ilyautov/small-business-ru/call-list"><img src="https://agentmods.dev/badge/skills/ilyautov/small-business-ru/call-list/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/ilyautov/small-business-ru/call-list"><img src="https://agentmods.dev/badge/skills/ilyautov/small-business-ru/call-list.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.00093 | $0.01192 |
| Opus 5 | $0.00046 | $0.00596 |
| Sonnet 5 | $0.00019 | $0.00238 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
call-list 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 10d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Утро уходит на «с кого бы начать», а горячие лиды ждут. Скилл сам сканирует воронку, ранжирует по срочности и потенциалу, подтягивает контекст из переписки и выдаёт готовый список звонков с тезисами — садись и набирай.
Разбери аргументы:
--n(по умолчанию:5) — сколько лидов вывести (1–10)--date(по умолчанию: сегодня) — на какую дату строить список звонков (ДД.ММ.ГГГГ)
Шаг 1 — Скан воронки
По рабочему процессу скилла lead-triage:
- Подтяни открытые сделки и контакты из
~~crm(например, Битрикс24 или amoCRM) с активностью за последние 30 дней. - Подтяни переписку из
~~почта(например, Яндекс 360) по каждому лиду (последние 3 письма на контакт). - Оцени каждый лид по:
- Свежесть: дней с последнего касания собственника (меньше = лучше)
- Стадия: насколько близко к закрытию (более поздняя стадия воронки = выше приоритет)
- Сигнал: любая недавняя входящая активность (открытие письма, ответ, бронь в календаре, визит на сайт)
- Сумма: сумма сделки в ₽ из
~~crm
Шаг 2 — Ранжируй и выбери топ N
Отранжируй все оценённые лиды и выбери топ --n. При равенстве баллов отдавай приоритет лидам с неотвеченными входящими сигналами.
Для каждого выбранного лида сделай карточку звонка:
{Ранг}. {Имя контакта} — {Компания}
Сделка: {сумма} ₽ | Стадия: {стадия} | Последний контакт: {X дней назад}
Сигнал: {последняя активность}
ТЕЗИСЫ
• {тезис из переписки/контекста сделки}
• {тезис из переписки/контекста сделки}
• {открытый вопрос, который стоит задать}
ЦЕЛЬ ЗВОНКА: {одно предложение — продвинуть на следующую стадию / реактивировать / закрыть}
Шаг 3 — Блок в календаре
Для каждого лида из списка предложи забронировать 20 минут в ~~календарь собственника (например, Яндекс Календарь) на целевую дату.
Покажи предлагаемые записи в календаре:
{временной слот} — Звонок: {Имя контакта} ({Компания})
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.
- 10d ago First seen · 88 lines · 93 tokens per session scan A 4893670a514d
call-list is a skill published in the GitHub repository ilyautov/small-business-ru (15 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 93 tokens to every session and 1,192 once invoked, about $0.0005 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-30.
Other skills, from other repositories
auto-research
Research uncertain questions with an explicit, user-approved web search or ChatGPT consultation, then present options and wait for implementation approval.
socialclaw
Use when a user wants social media scheduling and publishing for AI agents on X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest through SocialClaw.
socialclaw
Use when a user wants social media scheduling and publishing for AI agents on X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest through SocialClaw.
socialclaw
Schedule and publish social media posts across X, LinkedIn, Instagram, Facebook Pages, TikTok, YouTube, Reddit, Pinterest, WordPress, Discord, and Telegram. Use when the user wants to post, schedule, or publish to social media, or check post status and analytics.
ui-design-engineering
Design, implement, harden, and review production-grade user interfaces for web apps, dashboards, SaaS products, admin tools, forms, and responsive frontend components. Use when building or improving UI/UX, translating Figma or requirements into code, styling React/Vue/Svelte/HTML views, reviewing frontend quality…
repo-tour
Use after graphify has already built graphify-out/graph.json for a project, to generate a dependency-ordered guided tour, an onboarding doc for new team members, or a diff-impact analysis before a commit/PR — reading the existing graph instead of re-scanning the repo. Trigger on "onboarding guide"…