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 agentmods add skills/jtprogru/bear-skills/content-article-draftnpx skills add jtprogru/bear-skills --skill content-article-draftgit clone --depth 1 https://github.com/jtprogru/bear-skillsWrote 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/jtprogru/bear-skills/content-article-draft)<a href="https://agentmods.dev/skills/jtprogru/bear-skills/content-article-draft"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/content-article-draft.svg" alt="Measured on agentmods" 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.00102 | $0.01347 |
| Opus 5 | $0.00051 | $0.00674 |
| Sonnet 5 | $0.00020 | $0.00269 |
| Haiku 4.5 | $0.00010 | $0.00135 |
Grade A, and why
content-article-draft 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 5d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
content-article-draft — Драфт статьи
Цель: превратить материал в первый рабочий драфт статьи 3-10 тыс. символов. Не финальную версию — её пользователь шлифует сам. Драфт должен иметь правильный скелет и тон.
Перед началом прочитай:
~/.claude/rules/content-voice.md~/.claude/rules/content-formatting.md— раздел про статьи
Шаг 1. Контекст
Спроси:
- тема в одно предложение
- аудитория: технические специалисты определённого уровня? Менеджеры? Начинающие?
- платформа: Habr / Medium / dev.to / личный блог / Telegraph?
- исходник: заметки, опыт, проект, существующий драфт?
- цель статьи: научить чему-то / поделиться опытом / разобрать кейс / провокация-эссе?
Шаг 2. Сформулируй тезис
Тезис статьи — одно утверждение, которое автор защищает или иллюстрирует. Не тема, а утверждение.
| Тема (плохо) | Тезис (хорошо) |
|---|---|
| «Микросервисы» | «Микросервисы стоят сложности только когда у тебя реально разные циклы релизов или языки» |
| «Postgres vs Mongo» | «Для большинства стартапов Postgres покрывает 95% задач, а оставшиеся 5% не оправдывают второй БД» |
| «Опыт работы с k8s» | «Через год с k8s в проде я понял, что главный риск — не сложность, а размытие ответственности SRE vs dev» |
Покажи тезис пользователю и попроси подтвердить или поправить. Тезис — фундамент.
Шаг 3. Сложи скелет
Стандартная структура:
# <Заголовок>
> **TL;DR:** <тезис в 1-2 фразах + краткий итог>
## <Подзаголовок 1: контекст / проблема>
<Почему это интересно. Конкретный пример из жизни.>
## <Подзаголовок 2: аргумент / разбор / решение>
<Главная мысль. Код, схемы, числа.>
## <Подзаголовок 3: нюансы / контраргументы>
<Где тезис не работает. Где есть оговорки.>
## <Подзаголовок 4: применение / итог>
<Что читатель может сделать со всем этим.>
---
<подпись / автор / ссылки на ресурсы>
Покажи скелет (заголовок + подзаголовки + 1-фразовое описание каждой секции) и спроси, подходит ли. Не переходи к написанию текста, пока скелет не согласован.
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.
- 5d ago First seen · 131 lines · 102 tokens per session scan A 174e6463f35a
content-article-draft is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 18d ago), licensed MIT. It adds 102 tokens to every session and 1,347 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-31.
Other skills, from other repositories
content-planner
GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks…
setup-cms
Connect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my…
broken-link-checker
Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
google-ads-copy
Generate and A/B test Google Ads copy. Use when asked to write ad copy, headlines, descriptions, create ad variants, test ad messaging, improve CTR, or generate RSA (Responsive Search Ad) components. Trigger on "ad copy", "write ads", "headlines", "descriptions", "RSA", "responsive search ad", "ad text", "ad…
hreflang-international
International / multilingual SEO audit focused on hreflang correctness. Detects and diagnoses the most common (and ranking-damaging) hreflang mistakes: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, conflicts between hreflang and canonical, and inconsistent…