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/timurgaleev/memex/schema-authornpx skills add timurgaleev/memex --skill schema-authorgit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/schema-author)<a href="https://agentmods.dev/skills/timurgaleev/memex/schema-author"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/schema-author.svg" alt="Measured on agentmods" 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 | $0.00069 | $0.02870 |
| Opus 5 | $0.00034 | $0.01435 |
| Sonnet 5 | $0.00014 | $0.00574 |
| Haiku 4.5 | $0.00007 | $0.00287 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
schema-author — evolve the brain's type taxonomy
memex uses OPEN page typing: a page's type lives in its frontmatter, filing
prefixes are conventions (see _brain-filing-rules.md), and typed links are
derived from page content. There is no mutable "pack" artifact — the taxonomy
is the set of conventions the ontology tracks plus the frontmatter discipline
this skill enforces. Authoring the taxonomy means: read the active ontology,
propose changes through it, record the convention, and backfill existing pages.
Non-goals (use these other skills instead)
This skill AUTHORS the taxonomy (adds page types, link verbs, filing prefixes, expert-routing decisions). For these adjacent jobs, route elsewhere:
- Filing one specific page →
skills/brain-taxonomist(viaget_skill brain-taxonomist). Brain-taxonomist routes at WRITE TIME ("where does this note go?"). schema-author changes the rules at AUTHORING TIME ("what types and prefixes exist?"). - Taxonomy-check as part of EIIRP iteration →
skills/eiirpalready has a schema-check phase. Don't duplicate. - Just looking up a type's settings →
ontology_get(orontology_dimensionsfor the dimension breakdown) directly. This skill is for CHANGING the taxonomy, not READING from it. - Querying who knows about X →
find_expertsdirectly (or the expert-routing conventions). schema-author decides that a type should be expert-routable; it does not run the query.
Convention
Convention: see
conventions/brain-first.md(viaget_skill conventions/brain-first) for the lookup chain (search → query → page_get → external).
Convention: see
conventions/schema-evolution.md(viaget_skill conventions/schema-evolution) 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 taxonomy" - "I have 4000 untyped pages under
meetings/" - "My brain doesn't know that
journal-articleis a type" - "Treat
paperpages as fact-extractable" - "Propose types from what I've ingested"
- "Backfill the new types onto existing pages"
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.
- 4d ago First seen · 289 lines · 69 tokens per session scan A 09a64a2665c5
schema-author is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 2,870 once invoked, about $0.0003 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-31.
Other skills, from other repositories
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
grounded-knowledge-workflow
Use Grounded Knowledge Engine to select an isolated workspace, answer from local evidence, resume an explicitly identified project, create an explicit project checkpoint, and retain durable knowledge. Trigger when a user asks about their documents, workspace or client context, previous research, project state…
weasley-deepmind
AI 에이전트가 weasley-deepmind 기억 서버를 최대 효율로 활용하기 위한 기술 레퍼런스.
knowledge-capture-policy
Decide when high-value work should become a Joplin pending capture draft through joplin-llm-wiki MCP tools, without bypassing user confirmation.
gbrain-ingest
Ingest meetings, articles, docs, and conversations into the brain. Updates existing pages with new info, creates pages for new entities, maintains cross-references.
gbrain-query
Answer questions from the brain using FTS5 + semantic search + structured queries. Synthesizes across multiple pages with citations.