agentmods.dev

obsidian-split-note

obsidian-split-note is a skill for Claude Code from jtprogru/bear-skills. It costs 92 tokens per session (1,975 once invoked), scanned A, original, MIT.

A note-organizing workflow that splits a long Obsidian note or lecture summary into smaller linked notes while keeping the original connected.

In plain words
What is it for?
It is for breaking up lecture notes or other long notes, extracting standalone concepts, placing new notes in an inbox folder, and maintaining Obsidian links and metadata.
Why use it?
It makes large notes easier to review by separating distinct ideas without losing links between the source note and the new notes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the bear-skills plugin — 42 skills, 3 commands, 11 agents, 1 hook shipped together

not rated 1 18d ago A scan 92 tokens original MIT
View the source file jtprogru/bear-skills
Install

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.

agentmods
npx agentmods add skills/jtprogru/bear-skills/obsidian-split-note
Any agent
npx skills add jtprogru/bear-skills --skill obsidian-split-note
Clone the repo
git clone --depth 1 https://github.com/jtprogru/bear-skills

Made for: Claude Code.

Or install bear-skills, the plugin that ships this one along with the rest of its 42 skills, 3 commands, 11 agents, 1 hook.

Wrote 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.

agentmods badge for obsidian-split-note

README.md
[![agentmods](https://agentmods.dev/badge/skills/jtprogru/bear-skills/obsidian-split-note.svg)](https://agentmods.dev/skills/jtprogru/bear-skills/obsidian-split-note)
Your own site
<a href="https://agentmods.dev/skills/jtprogru/bear-skills/obsidian-split-note"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/obsidian-split-note.svg" alt="Measured on agentmods" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,975 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.01975
Opus 5 $0.00046 $0.00988
Sonnet 5 $0.00018 $0.00395
Haiku 4.5 $0.00009 $0.00198

Measured 5d ago against content hash 679596c1d54f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

obsidian-split-note 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.

domains/obsidian/skills/obsidian-split-note/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

obsidian-split-note

Разбивает одну большую заметку на несколько меньших (атомарных или тематических), сохраняя связность:

  • оригинал остаётся, его разделы заменяются на краткое описание + [[wikilink]];
  • каждая новая заметка создаётся в правильной папке по PARA;
  • frontmatter оригинала и новых заметок согласованы (up/down проставлены).

Базовые правила (PARA, теги, frontmatter, стиль, имена файлов) — в .agents/rules/. Особенно: tags.md (раздел «Структурные теги»), note-types-frontmatter.md, навык /knowledge-structures (атомарные заметки), file-naming.md.

Алгоритм

1. Прочитай и определи кандидатов

Критерии «выделять / оставить» — навык /knowledge-structures (раздел «Когда выделять раздел в отдельную заметку»). Определи общую тему оригинала и список кандидатов.

2. Покажи план и дождись подтверждения

Протокол план → подтверждение → действие — workflows.md. Формат плана:

Дочерние заметки создаются в 00. Входящие/; в плане показывай целевую папку справочно (workflows.md, «Новые заметки рождаются во входящих»).

Оригинал: [[Название]] (остаётся на месте, тема: …)
Выделить (все → 00. Входящие/):
  1. [[Имя новой 1]] — #thought #review → 03. Ресурсы/04. Заметки/
  2. [[Имя новой 2]] — #MapOfContent #review → 03. Ресурсы/07. Карты/
Оставить в оригинале: вводный абзац, короткое заключение

3. Создай дочерние заметки

Для каждой:

  1. Имя файла — см. file-naming.md. Для серии из одного источника: <Родитель> – <Концепт>.md. Для самостоятельной: содержательное claim-based имя.
  2. Папка — всегда 00. Входящие/. Структурный тег ставим финальный по tags.md (обычно #thought, целевая папка 03. Ресурсы/04. Заметки/) и добавляем #review: по этой паре obsidian-refactor-inbox потом перенесёт файл. Wikilinks резолвятся по имени файла, поэтому ссылки из оригинала работают сразу.
  3. Frontmatter — заведи файл через Templater по соответствующему шаблону из _Система/1. Шаблоны/, поля дозаполни Edit-ом; рецепт вызова и грабли — навык /note-templates, раздел «Как применить шаблон технически». Шапку по памяти не собирай. В up — wikilink на оригинал. Поставь ai_generated: true и заполни summary — 1–3 предложения сути в claim-стиле, plain text без wikilinks (см. политики в note-types-frontmatter.md).
  4. Тело — перенеси содержимое раздела под заголовком ## Суть (или ## Идея / ## Определение по типу). Переносишь, а не разворачиваешь: пояснений, вводных и закруглений, которых не было в оригинале, не добавляй. Пустые секции шаблона удаляй (note-density.md).
  5. Перед созданием — rg -l "Название концепта" . чтобы не плодить дубликаты.

Read the full file on GitHub · 108 lines

Files

What ships with it

2 files 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.

Changes

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.

  1. 5d ago First seen · 108 lines · 92 tokens per session scan A 679596c1d54f

Subscribe to this mod's changes

obsidian-split-note is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 18d ago), licensed MIT. It adds 92 tokens to every session and 1,975 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.

ProductivityWriting and docsagentopsagentsai-agentsclaude-codeclaude-code-plugin
Related

Other skills, from other repositories

session-handoff

Write a handoff file so a stuck session can resume in the other tool without losing context. Use when asked to "hand this off", "switch to Codex", "switch to Claude Code", "write a handoff", "I'm stuck, try the other tool", or when a session has burned several attempts on the same problem.

runnithan/claudex-setup · 72 tokens

configuring-grove

Use when a user wants to set up or change Grove's configuration, for a host/user or for a project. Covers the global user config, the committed project config, machine-local overrides, agents, init scripts, containers, tmux and peek tuning, the TUI theme, the daemon auth, notifications, and ticket providers (Gitea…

bearlike/Grove · 122 tokens

meta-tags-optimizer

Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…

nowork-studio/notfair-plugin · 91 tokens

add-teams

Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.

microsoft/power-platform-skills · 31 tokens

paid-ads-linkedin

Audit, diagnose, plan, and safely operate connected LinkedIn Ads accounts through the NotFair MCP, with an export-based fallback. Use for LinkedIn advertising, sponsored content, lead-generation forms, job-title or company targeting, campaign groups, creatives, conversions, lead quality, budgets, bids, or approved…

nowork-studio/notfair-plugin · 72 tokens

sxo

Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…

nowork-studio/notfair-plugin · 235 tokens