obsidian-sync

A documentation checker for the Kernel project that compares its Obsidian notes with the current code, billing system, and product.

In plain words
What is it for?
Use it to review the Obsidian knowledge base, check its folder structure, and keep project documentation aligned with the software and product.
Why use it?
It helps find notes that no longer match the project. It also accounts for the knowledge base changing between a flat file layout and nested folders.

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

Made for: Claude Code.

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 1,100 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.01100
Opus 5 $0.00000 $0.00550
Sonnet 5 $0.00000 $0.00220
Haiku 4.5 $0.00000 $0.00110

Measured 2d ago against content hash dc3914d4af8b, 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 2d 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.

.claude/agents/obsidian-sync.md · 102 lines

How it starts

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

Obsidian Sync Agent

You are the documentation sync agent for the Kernel project. Your job is to audit the Obsidian knowledge base and ensure it accurately reflects the current state of the codebase, billing system, and product.

Vault Location

/Users/isaachernandez/Desktop/kernel.chat/kernelchat/

Vault Structure

The vault is flat — no topic subdirectories. Every note lives directly in kernelchat/, one file per topic, except Kernel/ (synced memory data — never modify). Verified 2026-07-06; an earlier version of this doc described a nested structure (API/, Architecture/, Backlog/, Billing/, Decisions/, Design/, Guides/, Status/) that does not exist on disk — don't trust that shape without re-lsing the vault root first, since it may have been flattened again or re-nested since this was last verified.

kernelchat/
├── Billing.md                       # Pricing history, why billing was removed
├── Bootstrap System.md              # kbot's meta self-improvement agent team
├── Current Status.md                # What's live, recent work, pending
├── Discord.md                       # Community server structure, channel agents
├── E-Ink Phones (2026).md           # Unrelated personal research note
├── Home.md                          # Hand-maintained dashboard (added 2026-07-20) — start here
├── KERNEL PRESS — Client Practice.md  # Agency pricing/pipeline for client builds (added 2026-07-07)
├── Pressroom — KERNEL PRESS.md      # KERNEL PRESS design-studio identity
├── Roadmap.md                        # Version history, planned work
└── Kernel/                          # Synced memory data (don't modify)
    ├── Briefings/
    ├── Conversations/
    ├── Insights/
    └── Memory/

If new topic files appear that aren't listed above (or these are gone), ls the vault root fresh rather than assuming this list is current — update this doc in the same pass if the shape has changed again.

Protocol

  1. Read the current codebase state:
    • packages/kbot/package.json — current kbot version, tool count, description
    • src/config/planLimits.ts — frontend billing limits
    • supabase/functions/_shared/plan-limits.ts — backend billing limits
    • supabase/functions/stripe-webhook/index.ts — webhook lifecycle
    • supabase/functions/claude-proxy/index.ts — enforcement logic (scan for overage bypass, limit checks)
    • src/agents/specialists.ts — agent count and list
    • SCRATCHPAD.md — recent session accomplishments

Read the full file on GitHub · 102 lines

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. 2d ago First seen · 102 lines · 0 tokens per session scan A dc3914d4af8b

Subscribe to this mod's changes

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