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 voxpelli/vp-claude --skill schema-evolvegit clone --depth 1 https://github.com/voxpelli/vp-claudeWrote 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/voxpelli/vp-claude/schema-evolve)<a href="https://agentmods.dev/skills/voxpelli/vp-claude/schema-evolve"><img src="https://agentmods.dev/badge/skills/voxpelli/vp-claude/schema-evolve.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.1 | $0.00139 | $0.04708 |
| Opus 5 | $0.00069 | $0.02354 |
| Sonnet 5 | $0.00028 | $0.00942 |
| Haiku 4.5 | $0.00014 | $0.00471 |
Grade A, and why
schema-evolve 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 6d 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Evolution
Detect drift between a Basic Memory schema definition and actual note usage,
propose changes, and synchronize both the BM schema note and the local
schemas/ file after user approval.
Arguments
Required: the note type in snake_case.
| Example | Schema file |
|---|---|
npm_package |
schemas/npm_package.md |
brew_formula |
schemas/brew_formula.md |
github_action |
schemas/github_action.md |
engineering |
schemas/engineering.md |
standard |
schemas/standard.md |
The argument must match a type value used in Basic Memory note frontmatter
and a corresponding file in schemas/. If the type is unknown, list available
schema files and ask the user to pick one.
Optional: --prescribed verb1,verb2,... — force-add specified relation
verbs (or observation field names) to the schema regardless of usage
frequency. See "Modes" below.
Modes
The skill operates in two complementary modes:
Drift-driven mode (default)
Invocation: /schema-evolve <note_type>
Frequency-based: schema_diff and schema_infer decide what to add or
remove. Fields are added only when their actual per-type usage crosses
the 25% threshold. This is the right mode for organic schema evolution
where the notes lead and the schema catches up.
Limitation: prescribed cross-schema vocabulary (e.g., a Tier-0 verb set that should be declared identically across many schemas) cannot be absorbed this way until each schema independently crosses 25% — which may never happen for narrow types.
Prescribed mode
Invocation: /schema-evolve <note_type> --prescribed verb1,verb2,...
Frequency-bypass: the listed names are force-added to the target schema regardless of usage. Intended for absorbing cross-schema vocabulary (Tier-0 verbs the operator wants declared uniformly across schemas) or for adding fields ahead of authoring practice.
The two modes compose: in a single invocation, prescribed additions are
applied alongside drift-driven proposals. Removal and cardinality
proposals continue to come from schema_diff / schema_infer and are
unaffected by --prescribed.
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.
- 6d ago First seen · 423 lines · 139 tokens per session scan A 8923c2a78091
schema-evolve is a skill published in the GitHub repository voxpelli/vp-claude (3 stars, last pushed 9d ago), licensed MIT. It adds 139 tokens to every session and 4,708 once invoked, about $0.0007 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
synergy-tracker
Manage cross-project synergy tracking between sibling projects. Use when the user wants to log a shared pattern, a divergence, an extraction candidate, or something a sibling project has that this one doesn't. Also use when the user wants to promote synergy entries to Basic Memory (workflow 5). NOT for upstream…
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…
retrospective
Run a sprint retrospective for this project. Use when the user says 'retrospective', 'retro', 'close out the sprint', 'what went well', 'generate retro', or wants to generate a RETRO-NN.md file. Reads UPSTREAM-.md files, recent git history, and conversation context to pre-populate the retrospective. Do NOT use for…
swarm-wave
Orchestrate multi-agent development sprints with wave-based parallelism. Use when the user wants to plan a swarm sprint, partition work into file-disjoint waves, map file contention across open issues, run a post-wave quality gate with review agents, manage agent backpressure, run a parallel research wave, or…
backlog-groomer
Manage the beads backlog for this project. Use when the user wants to review or triage open issues, reprioritize the backlog, identify obsolete issues to close, investigate a topic to inform future work, create new issues from research findings, or enrich an existing issue with external context. Trigger phrases…
harden-memories
Audit the bd remember store and recommend which entries to prune, so each one earns its per-session bd prime injection cost. Read-only: it proposes a triage table plus the exact bd forget / migration commands; you run them. Use when bd remember entries have accumulated, feel stale, redundant, or conflicting, or when…