schema-author

A guide for managing the vocabulary and rules used in an Open Second Brain vault, a structured collection of personal notes. It covers labels, aliases, links, and how notes are routed or extracted.

In plain words
What is it for?
Use it when adding, renaming, reviewing, or explaining note types and links, and when previewing or applying changes to the vault’s schema.
Why use it?
It helps keep the vault’s structure consistent before schema changes are made. It also provides checks for unused labels, errors, and possible replacements.

Skill for Claude CodeCodex

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/itechmeat/open-second-brain/schema-author
Any agent
npx skills add itechmeat/open-second-brain --skill schema-author
Clone the repo
git clone --depth 1 https://github.com/itechmeat/open-second-brain

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 458 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.00038 $0.00458
Opus 5 $0.00019 $0.00229
Sonnet 5 $0.00008 $0.00092
Haiku 4.5 $0.00004 $0.00046

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

Security

Grade A, and why

schema-author 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 3d 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.

skills/schema-author/SKILL.md · 24 lines

What it actually says

Schema Author

Use this skill when a task changes the active Brain schema pack in Brain/_brain.yaml or reviews content against that schema.

Workflow

  1. Inspect the active schema pack with schema_inspect (view="active_pack") or o2b brain schema --json.
  2. Check current usage and findings with schema_inspect views stats, lint, and orphans.
  3. Explain candidate tokens with schema_inspect (view="explain_type") before renaming or deleting them.
  4. Preview the batch first with schema_apply_mutations (dry_run=true) or o2b brain schema apply --dry-run --mutation ...: it returns the pack that would result and its diff and writes nothing at all - no config write, no audit record, no lock file. It runs the same pack validator the apply runs, so a batch that validator rejects raises identically in both. It does not run the two checks that exist only because the apply writes: the vault-identity write guard, and the atomic writer's re-parse of the rendered YAML. A batch that renders to unparseable YAML previews clean and fails on apply, so treat a clean preview as "the mutations are valid", not as "the apply will succeed".
  5. Apply schema changes only through schema_apply_mutations or o2b brain schema apply --mutation ... so writes are locked, atomic, and audited.
  6. Re-run lint/stats after mutation and report changed tokens plus any remaining findings.

Mutation Notes

Supported operations are add_type, remove_type, update_type, add_alias, remove_alias, add_prefix, remove_prefix, add_link_type, remove_link_type, set_extractable, and set_expert_routing.

Schema tokens must be lowercase normalized tokens accepted by Open Second Brain schema validation. Prefer small, durable tokens over project-specific phrasing unless the schema pack is explicitly project-scoped.

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. 3d ago First seen · 24 lines · 38 tokens per session scan A 2c37178a64e9

Subscribe to this mod's changes

schema-author is a skill published in the GitHub repository itechmeat/open-second-brain (385 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 458 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens