obsidian-sync

obsidian-sync is a command for Claude Code from isaacsight/kernel. It costs 0 tokens per session (324 once invoked), scanned A, original, MIT.

A command that compares an Obsidian knowledge base with selected source files in a codebase and updates documentation when they disagree.

In plain words
What is it for?
Use it to audit specified project and vault files, fix documented discrepancies, update dates, and report what changed or remained accurate.
Why use it?
It reduces drift between project documentation and the actual code, such as outdated versions, billing limits, agent lists, or feature descriptions.

Command for Claude Code

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 commands/isaacsight/kernel/obsidian-sync
Clone the repo
git clone --depth 1 https://github.com/isaacsight/kernel

Made for: Claude Code.

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-sync

README.md
[![agentmods](https://agentmods.dev/badge/commands/isaacsight/kernel/obsidian-sync.svg)](https://agentmods.dev/commands/isaacsight/kernel/obsidian-sync)
Your own site
<a href="https://agentmods.dev/commands/isaacsight/kernel/obsidian-sync"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/obsidian-sync.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 324 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.00000 $0.00324
Opus 5 $0.00000 $0.00162
Sonnet 5 $0.00000 $0.00065
Haiku 4.5 $0.00000 $0.00032

Measured yesterday against content hash cd6e04effbb3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

obsidian-sync 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 yesterday.

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.

.claude/commands/obsidian-sync.md · 39 lines

What it actually says

Audit the Obsidian knowledge base and sync it with the current codebase state.

You are the Obsidian Sync Agent. Read .claude/agents/obsidian-sync.md for your full protocol.

Steps:

  1. Read codebase state — Check these source-of-truth files:

    • packages/kbot/package.json — kbot version, description
    • src/config/planLimits.ts — frontend billing limits
    • supabase/functions/_shared/plan-limits.ts — backend billing limits
    • src/agents/specialists.ts — agent roster
    • SCRATCHPAD.md — recent session work
  2. Read all vault files at /Users/isaachernandez/Desktop/kernel.chat/kernelchat/

    • Skip Kernel/ data folders, .canvas, .base files
    • Check every .md file in: Status, Billing, API, Architecture, Decisions, Backlog, Design, Guides
  3. Compare and fix discrepancies — pricing, versions, agent counts, feature descriptions, completed/pending items

  4. Update stale files — edit content and bump updated date in frontmatter

  5. Report — list what was updated, what was already correct

Report format:

# Obsidian Sync Report — [date]

## Files Audited
[count]

## Updates Made
- [file]: [what changed]

## Still Accurate
- [list]

## Verdict: SYNCED / OUT OF SYNC
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. yesterday First seen · 39 lines · 0 tokens per session scan A cd6e04effbb3

Subscribe to this mod's changes

obsidian-sync is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 324 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-09-03.