knowledge-structures

knowledge-structures is a skill for Claude Code, Codex from jtprogru/bear-skills. It costs 84 tokens per session (1,615 once invoked), scanned A, original, MIT.

A system for organizing notes into navigation pages, synthesis notes, and small standalone notes. A map of content is a note that links together related notes around one topic.

In plain words
What is it for?
Use it to create topic maps, compare several ideas or tools, summarize larger sources, and split sections into focused notes.
Why use it?
It helps prevent large notes and scattered information from becoming difficult to navigate, compare, or reuse.

Skill for Claude CodeCodex

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

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/knowledge-structures
Any agent
npx skills add jtprogru/bear-skills --skill knowledge-structures
Clone the repo
git clone --depth 1 https://github.com/jtprogru/bear-skills

Made for: Claude Code, Codex.

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 knowledge-structures

README.md
[![agentmods](https://agentmods.dev/badge/skills/jtprogru/bear-skills/knowledge-structures.svg)](https://agentmods.dev/skills/jtprogru/bear-skills/knowledge-structures)
Your own site
<a href="https://agentmods.dev/skills/jtprogru/bear-skills/knowledge-structures"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/knowledge-structures.svg" alt="Measured on agentmods" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,615 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 $0.00084 $0.01615
Opus 5 $0.00042 $0.00807
Sonnet 5 $0.00017 $0.00323
Haiku 4.5 $0.00008 $0.00161

Measured 4d ago against content hash 76e8105a377d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

knowledge-structures 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 4d 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/knowledge-structures/SKILL.md · 103 lines

How it starts

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

Структуры знаний: MOC, синтез, атомарные заметки

MOC (Map of Content)

MOC — навигационная заметка, которая собирает ссылки по определённой теме. Главная MOC — README.md в корне. Тематические MOC лежат в 03. Ресурсы/07. Карты/; новую карту агент создаёт в 00. Входящие/ с #MapOfContent + #review и она переезжает в Карты после ревью (см. workflows.md).

Когда создавать MOC

  • Тема упоминается в 5+ заметках и нет единой точки входа
  • Пользователь явно просит создать карту по теме
  • Появляется новая крупная область знаний

Структура и правила MOC

Каркас — Шаблон карты.md в _Система/1. Шаблоны/. Обязательные секции: ## Описание (2–3 предложения своими словами), ## Ключевые заметки (ссылки с краткими аннотациями — не просто список, а список с контекстом), ## Связанные темы, ## Автосбор заметок (Dataview/Bases-запрос по ссылкам или тегу).

  • В up указывай родительскую MOC или область (если есть), в down — дочерние крупные подтемы
  • Добавляй Dataview-запрос для автоматического сбора связанных заметок

Синтез-заметки

Синтез — заметка, сравнивающая несколько концептов/инструментов/подходов и выдающая кросс-срезовый вывод. Хранится в 03. Ресурсы/07. Карты/, тег #synthesis. Как и карта, создаётся агентом в 00. Входящие/ с #review и переезжает после ревью.

Когда создавать синтез

  • Есть 2+ концепта/инструмента для сравнения
  • Появился инсайт, охватывающий несколько заметок сразу
  • Пользователь явно просит «сравни», «что лучше», «какой подход выбрать»

Структура и правила синтеза

Каркас: frontmatter с tags: [synthesis], sources, confidence + секции ## Сравнение (таблица по критериям), ## Анализ (кросс-срезовые выводы), ## Рекомендация (когда какой подход и почему), ## Связанные заметки (ссылки с пояснениями).

  • В sources перечисляй все исходные заметки; каждый вывод должен ссылаться на конкретные заметки
  • Если вывод основан на одной заметке — это не синтез, а атомарная мысль
  • При обновлении исходных заметок — проверяй актуальность синтеза

Read the full file on GitHub · 103 lines

Files

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.

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. 4d ago First seen · 103 lines · 84 tokens per session scan A 76e8105a377d

Subscribe to this mod's changes

knowledge-structures is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 16d ago), licensed MIT. It adds 84 tokens to every session and 1,615 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.

Related

Other skills, from other repositories

skill-doc-delivery

Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.

nyldn/claude-octopus · 29 tokens

skill-doc-sync

Post-ship doc sync across project markdown. Use when: sync docs, update docs, document changes, release notes.

nyldn/claude-octopus · 28 tokens

add-native

Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps…

microsoft/power-platform-skills · 96 tokens

add-pdf-report

Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.

microsoft/power-platform-skills · 30 tokens

doc-review

Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use codex-code-review), test review (use test-review). Output: 5-dimension rating table + gate.

sd0xdev/sd0x-harness · 56 tokens

handoff

Compacts the current conversation into one self-contained, tool-agnostic handoff document at docs/handoffs/ .md so any fresh agent or teammate can resume the work from that file alone. References pushed artifacts by path or URL, inlines anything not on the remote, and redacts secrets and PII. Re-running on an existing…

oprogramadorreal/optimus-claude · 86 tokens