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 jtprogru/bear-skills --skill obsidian-journal-reviewgit 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/obsidian-journal-review)<a href="https://agentmods.dev/skills/jtprogru/bear-skills/obsidian-journal-review"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/obsidian-journal-review/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/jtprogru/bear-skills/obsidian-journal-review"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/obsidian-journal-review.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.00083 | $0.01554 |
| Opus 5 | $0.00042 | $0.00777 |
| Sonnet 5 | $0.00017 | $0.00311 |
| Haiku 4.5 | $0.00008 | $0.00155 |
Grade A, and why
obsidian-journal-review 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 12d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
obsidian-journal-review
Анализ ежедневных заметок и формирование сводных обзоров (week / month / year). Базовые правила структуры, frontmatter и стиля — в .agents/rules/. Этот скилл фокусируется только на специфике дневника.
Триггеры: «сделай еженедельный обзор», «weekly review», «что было на этой неделе», «саммари недели», «посмотри ежедневные заметки», «journal review».
Контекст дневника
- Папка:
05. Дневник/ - Структура:
YYYY/MM/YYYY-MM-DD.md(например2026/03/2026-03-04.md) - Тег ежедневной:
#journal/daily(см..agents/rules/tags.md) - Шаблоны:
_Система/1. Шаблоны/Ежедневная заметка.md,Еженедельная заметка.md,Ежемесячная заметка.md,Ежегодная заметка.md
Навигация в шаблоне ежедневной:
**< [[2026-03-03|Вчера]] | [[2026-W10|Неделя]] | [[2026-M03|Месяц]] | [[2026-03-05|Завтра]] >**
Алгоритм ревью
1. Собери заметки за период
Прочитай все файлы из 05. Дневник/<год>/<месяц>/ за нужные даты. Для weekly — 7 заметок, для monthly — 4–5 weekly или все daily месяца, для yearly — 12 monthly.
2. Извлеки события
| Категория | Маркеры в тексте |
|---|---|
| 🎙️ Медийность | подкасты, съёмки, публикации, выпуски, статьи |
| 💼 Работа | проекты, встречи, решения, инциденты |
| 👥 Люди | wikilinks [[@username|Имя]] или просто [[Имя]] |
| 📚 Обучение | лекции, курсы, книги, доклады |
| 💡 Инсайты | «понял», «решил», «инсайт», «поймал себя» |
| ⚠️ Проблемы | «вызов», «риск», «проблема», «не получилось» |
| ✅ Достижения | «сделал», «закрыл», «выпустил», «защитил» |
| 📅 Задачи на потом | «к пятнице», «надо», «к [[YYYY-MM-DD]]» |
Сохраняй все wikilinks как есть — они критичны для графа.
3. Группируй и сжимай
Цель — саммари, не копипаст. Для каждой категории — 1–5 строк с wikilinks. Если в категории за период ничего — пропусти, не вставляй пустую секцию.
4. Создай или обнови сводную заметку
| Тип | Имя | Папка |
|---|---|---|
| Weekly | YYYY-Www.md (например 2026-W10) |
05. Дневник/<год>/<месяц понедельника недели>/ |
| Monthly | YYYY-MMM.md (например 2026-M03) |
05. Дневник/<год>/<месяц>/ |
| Yearly | YYYY.md |
05. Дневник/<год>/ |
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.
- 12d ago First seen · 133 lines · 83 tokens per session scan A 4ee755514928
obsidian-journal-review is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 1,554 once invoked, about $0.0004 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
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
docs-decisions
Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the…
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-review
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.
buyer-job-intent-analysis
Recover source-bound buyer jobs, struggling moments, desired progress, forces, workarounds, information acts, journey states, criteria, constraints, roles, locales, and authentic language. Use on approved ICP hypotheses plus customer, search, review, forum, procurement, support, or public-market evidence before…