Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/cynthiajones34/gbrain/schema-author)<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/schema-author"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/schema-author/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/schema-author"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/schema-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00067 | $0.03538 |
| Opus 5 | $0.00034 | $0.01769 |
| Sonnet 5 | $0.00013 | $0.00708 |
| Haiku 4.5 | $0.00007 | $0.00354 |
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 8d 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.
This is a copy
95% identical to schema-author — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
schema-author — evolve your schema pack
Non-goals (use these other skills instead)
This skill AUTHORS the schema pack (adds page types, link verbs, prefixes, flags). For these adjacent jobs, route elsewhere:
- Filing one specific page →
skills/brain-taxonomist/SKILL.md. Brain- taxonomist routes at WRITE TIME ("where does this note go?"). schema-author changes the rules at AUTHORING TIME ("what types and prefixes exist?"). - Schema-check as part of EIIRP iteration →
skills/eiirp/SKILL.mdalready has a schema-check phase. Don't duplicate. - Just looking up a type's settings →
gbrain schema explain <type>directly. This skill is for CHANGING the pack, not READING from it. - Querying who knows about X →
skills/expert-routing/SKILL.md(orgbrain whoknowsdirectly). schema-author makes a type expert-routable; it does not run the query.
Convention
Convention: see conventions/brain-first.md for the lookup chain (search → query → get_page → external).
Convention: see conventions/schema-evolution.md for "when to add a type vs alias vs prefix" — the heuristic.
When to invoke
Invoke when the user (or a sibling skill) says any of:
- "Add a
researchertype to my schema" - "I have 4000 untyped pages under
meetings/" - "My brain doesn't know that
journal-articleis a type" - "Set
paperto be extractable" - "Propose types from what I've ingested"
- "Sync the new types to backfill existing pages"
DON'T invoke for "where does THIS note go" (use brain-taxonomist) or
"who knows about X" (use expert-routing / gbrain whoknows).
Tutorial + vision
- Why this matters:
docs/what-schemas-unlock.md— 7 killer use cases (4000 invisible meetings made queryable, founder ops brain, research brain, legal brain, team brain, agent-as-co-curator) plus the structural argument for why types matter at query time. Read this before pitching schema authoring to a user — it's the doc that explains the difference between a pile of notes and a brain with structure. - 5-minute walkthrough:
docs/schema-author-tutorial.md— fork the bundled pack, add a researcher type, sync, prove the T1.5 wiring viagbrain whoknows. Use placeholder pages so it runs against any brain without affecting real content.
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.
- 8d ago First seen · 306 lines · 67 tokens per session scan A 4da9a472c966
schema-author is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 3,538 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to schema-author, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
memory-proactive
Proactive layered recall and generic domain-aware routing.
memory-archivist
A set of scripts for archiving conversations, syncing them to a knowledge graph, updating summaries, and managing stored memories over time. A knowledge graph is a linked collection of information and relationships.
memory-starter-kit
Historical starter note for the memory sidecar stack.
mind
Local project memory with recall, provenance, policy, and dreams.
personal-knowledge-graph
Use when maintaining a LoomKG/Obsidian knowledge graph.
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.