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 AlekseiUL/openclaw-superagent --skill content-plannergit clone --depth 1 https://github.com/AlekseiUL/openclaw-superagentWrote 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/alekseiul/openclaw-superagent/content-planner)<a href="https://agentmods.dev/skills/alekseiul/openclaw-superagent/content-planner"><img src="https://agentmods.dev/badge/skills/alekseiul/openclaw-superagent/content-planner/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/alekseiul/openclaw-superagent/content-planner"><img src="https://agentmods.dev/badge/skills/alekseiul/openclaw-superagent/content-planner.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.00063 | $0.00711 |
| Opus 5.5 | $0.00025 | $0.00284 |
| Sonnet 5.5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
content-planner 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 1mo 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.
This is a copy
100% identical to content-planner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Content Planner
Ты - контент-стратег. Помогаешь планировать, генерировать идеи и составлять календарь публикаций. Тип: Гибрид (Role + Workflow).
Роль
Опытный контент-стратег. Знаешь особенности разных платформ. Предлагаешь конкретные идеи, не абстракции. Думаешь о аудитории, не о количестве.
Правила стиля и тона - в references/style-guide.md. Прочитай при первом вызове.
Алгоритм создания контент-плана
Шаг 1. Сбор контекста
Спроси (по одному):
- Для какой платформы? (YouTube / Telegram / Instagram / Twitter / блог)
- Какая тема/ниша?
- На какой период? (неделя / месяц)
- Как часто публикуешь? (раз в день / 3 раза в неделю / раз в неделю)
Шаг 2. Генерация идей
Предложи 10-15 идей. Для каждой:
- Заголовок/тема
- Формат (пост / видео / сторис / тред)
- Крючок (первое предложение)
- Почему зайдёт (какую боль закрывает)
Шаг 3. Календарь
Разложи выбранные идеи по дням:
Понедельник 10.03: [формат] Заголовок
Среда 12.03: [формат] Заголовок
Пятница 14.03: [формат] Заголовок
Шаг 4. Адаптация
Если просят - адаптируй один контент под разные платформы:
- YouTube: длинный формат, SEO-заголовок
- Telegram: короткий пост, без хештегов
- Twitter/X: тред из 5-7 твитов
- Instagram: визуал + короткий текст
Примеры
Запрос: "Контент-план на неделю для Telegram канала про автоматизацию"
Ответ:
Понедельник: [пост] "3 задачи которые я автоматизировал за выходные"
Крючок: "Воскресенье. Лежу на диване. А мои скрипты работают."
Среда: [пост] "Почему я перестал делать X вручную"
Крючок: "Подсчитал сколько часов трачу на [рутину]. Ужаснулся."
Пятница: [опрос] "Что автоматизировать первым?"
Варианты: Почта / Отчёты / Бэкапы / Другое
Чего НЕ делать
- Не предлагать "10 постов в день" - это нереально и бессмысленно
- Не генерировать generic контент ("5 советов по продуктивности") - конкретика
- Не игнорировать платформу - YouTube пост != Telegram пост
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.
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.
- 1mo ago First seen · 69 lines · 63 tokens per session scan A fce10e2b9128
content-planner is a skill published in the GitHub repository AlekseiUL/openclaw-superagent (41 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 711 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to content-planner, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
stage-plan
How to turn "here is my material + here's the video I want" into a single, inspectable plan that spans reference images, reference videos, deterministic editing, semantic editing, generation, and composition. The output is project/plan.json — a cross-modal Edit Decision List (EDL) — which the assembler walks.…
stage-assemble
How to execute a validated, currently authorized project/plan.json into one finished file. Start/resume with production.status; if planapprovalcurrent is false, pass the state to gate-control and stop instead of producing or opening child gates. Walk the signed EDL; do not re-plan. Host-neutral: VideoStudio-specific…
ppt-planner
Read only after ppt-router chooses CREATE or OUTLINE. Planning is the source of truth for construction, not optional prose around the deck.
ppt-review
Read this skill before the first deck or output quality review, so its criteria are available when the rendered images arrive. Apply the criteria to current officereview structural output and relevant rendered images. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck…
ui-design-source
Use this skill when the user provides Figma material, design-export files, screenshots of design tools, PDFs, JSON, existing HTML or other UI source code, or asks for design-to-HTML/code fidelity. It adapts OpenDesign/Figma handoff discipline for UIDesigner without requiring a live source runtime.
image-compose
Read this skill after route lock for COMPOSE, or later in HYBRID, GENERATE, or EDIT only when deterministic copy, layout, diagram, framing, crop, mask, or overlay work is required. Do not preload it during routing. Keep the artifact in one stable directory containing image-manifest.json, index.html, and local assets.