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 dzhokhov/markdown-agent-vault-ru --skill personal-brand-contentgit clone --depth 1 https://github.com/dzhokhov/markdown-agent-vault-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/dzhokhov/markdown-agent-vault-ru/personal-brand-content)<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/personal-brand-content"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/personal-brand-content/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/dzhokhov/markdown-agent-vault-ru/personal-brand-content"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/personal-brand-content.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.00000 | $0.01396 |
| Opus 5 | $0.00000 | $0.00698 |
| Sonnet 5 | $0.00000 | $0.00279 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
personal-brand-content 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 11d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Скилл: Personal Brand Content
Назначение
Создание и адаптация экспертного контента для личного бренда или экспертного канала. Скилл помогает: генерировать контент по идее из очереди, адаптировать мастер-версию под конкретную платформу, поддерживать единый голос автора.
Когда использовать
Триггеры:
- «напиши пост про [тема] для [платформа]»
- «адаптируй [контент] для [платформа]»
- «новая идея: [текст]»
- «что постить?»
- «обработай бэклог»
- «weekly review»
- «обнови метрики»
Контекст проекта
Обязательно прочитать перед работой:
<project>/context.md— ниша, аудитория, столпы, форматы<project>/pipeline.md— методология контентного процесса, если есть<project>/platforms/{platform}.md— профиль целевой платформы, если есть
Голос автора (Author Voice)
Тон: Экспертный, но доступный. Как разговор с умным коллегой за кофе.
Принципы:
- Конкретика > абстракция. Всегда «было → стало → результат», а не «AI — это будущее»
- Опыт > мнение. Рассказывай что сделал, а не что думаешь
- Польза > хайп. Каждый пост должен давать что-то полезное: инструмент, подход, инсайт
- Честность > позитив. Не скрывать провалы и ограничения
- Простота > умничанье. Сложные вещи простым языком
Запрещено:
- Вода, штампы, канцелярит
- «В современном мире...», «Не секрет что...», «Все мы знаем...»
- Кликбейтные заголовки без содержания
- Общие советы без конкретики
- Самовосхваление без доказательств
Процесс создания контента
Шаг 1: Определи вводные
Прочитай идею из backlog или запрос пользователя. Определи:
- Контентный столп (pillar)
- Формат
- Целевая платформа(ы)
Шаг 2: Создай мастер-версию
Напиши полную версию контента без ограничений формата. Включи:
- Заголовок (3 варианта)
- Основной текст с конкретикой
- CTA (если уместен)
- Источники / ссылки
Сохрани в: content/YYYY-MM-DD-slug-master.md
Шаг 3: Адаптируй под платформу
Загрузи профиль платформы из platforms/{platform}.md. Адаптируй:
- Длину (по лимитам платформы)
- Форматирование (markdown, HTML, plain text)
- Тон (более/менее формальный)
- Хештеги / теги
- CTA (подписка, комментарий, репост — по паттернам платформы)
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.
- 11d ago First seen · 145 lines · 0 tokens per session scan A f830cad11f3b
personal-brand-content is a skill published in the GitHub repository dzhokhov/markdown-agent-vault-ru (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,396 tokens. 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
pos-verify
Use this immediately after files are created, edited, moved, deleted, or materially rewritten inside PersonalOS. Verifies that new truth was routed to the correct owner, written in the correct file shape, and still follows POS conventions. Do NOT use for whole-vault deep audits; use system-health-check.
skillify
Use this when {{username}} asks to skillify a repeated workflow, determine whether it deserves a reusable PersonalOS skill, or harden an existing workflow into a tested resolver-reachable capability. Do NOT use for one-off notes, ordinary execution, or already-specified skill authoring; use write-skill.
write-skill
Use this when the user wants to create a new shared PersonalOS skill under skills/ or revise a specified PersonalOS skill and the scope is already clear. Do NOT use for raw workflow capture or deciding whether work should become a skill; use skillify first. Do NOT use for repo-local or agent-local skills unless…
priority-dashboard
Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.
log
Use this when a PersonalOS work session, chat outcome, personal reflection, or provided source should be persisted into the modular Daily context and any already-owned canonical files. Do NOT use for single-call processing, single-source knowledge ingestion, Gmail/WhatsApp propagation, or Lexware booking.
task-manager
Use this when {{username}} or an agent wants to add, review, prioritize, complete, defer, park, or inspect todos, open loops, confirmed actions, waiting states, or attention triggers. Maintains atomic records under operations/actions/ and operations/attention-triggers/ as the only local action truth. Do NOT use for…