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.
npx agentmods add skills/itechmeat/open-second-brain/schema-authornpx skills add itechmeat/open-second-brain --skill schema-authorgit clone --depth 1 https://github.com/itechmeat/open-second-brainWhat 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.
| Model | Per session | Once 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 |
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.
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
- Inspect the active schema pack with
schema_inspect(view="active_pack") oro2b brain schema --json. - Check current usage and findings with
schema_inspectviewsstats,lint, andorphans. - Explain candidate tokens with
schema_inspect(view="explain_type") before renaming or deleting them. - Preview the batch first with
schema_apply_mutations(dry_run=true) oro2b 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". - Apply schema changes only through
schema_apply_mutationsoro2b brain schema apply --mutation ...so writes are locked, atomic, and audited. - 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.
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.
- 3d ago First seen · 24 lines · 38 tokens per session scan A 2c37178a64e9
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…