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 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/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/timurgaleev/memex/schema-author"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/schema-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 253 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00069 | $0.02956 |
| Opus 5.5 | $0.00028 | $0.01182 |
| Sonnet 5.5 | $0.00014 | $0.00591 |
| Haiku 4.5 | $0.00007 | $0.00296 |
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 1mo 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 — 287 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.
- 1mo ago Changed · -2 lines 7785f71462a1
- 1mo ago First seen · 289 lines · 69 tokens per session scan A 09a64a2665c5
schema-author is a skill published in the GitHub repository timurgaleev/memex (11 stars, last pushed 29d ago), licensed MIT. It adds 69 tokens to every session and 2,956 once invoked, about $0.0003 per session on Opus 5.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
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
weasley-deepmind
A reference for using weasley-deepmind, a server that stores and retrieves an AI agent’s long-term memories between sessions. It describes memory storage, search, language processing, and related tools.
thebrain-ingest
Lay material into TheBrain as a connected graph rather than a pile of notes. Use when asked to "put this article in my brain", "save this", "add it to the knowledge base", "break this down and record it" — about an article, a document, a discussion, a research result or the user's own thinking. Covers: how finely to…
thebrain-organize
Tidy up TheBrain: find duplicates, thoughts with no links, empty stubs, scattered branches about the same thing. Use when asked to "clean up my brain", "find duplicates", "what is dangling with no links", "sort this out", "the structure has drifted". Covers: how to hunt for disorder, what you may fix yourself, and…
thebrain-digest
Report what happened in the brain over a period, and what deserves going back to. Use when asked "what did I add this week", "show me a digest", "what have I been working on", "what is new in the brain", and at the start of a session when the context of previous work needs recalling. Covers: how to read the…
thebrain-research
Use TheBrain as a knowledge base when answering a question: look at what is already known first, and only then reason. Use when asked "what do I know about X", "what do I have on this topic", "have we discussed this already", "remind me what we concluded", and before any substantive answer on a topic that might be in…